Printer having printhead with multiple controllers

ABSTRACT

A printer is provided having a printhead having ejection nozzles and a plurality of controllers configured to process print data for printing and to output the processed data to the printhead. The plurality of controllers are connected to a common input of the printhead.

CROSS REFERENCE TO RELATED APPLICATION

The present application is a Continuation of U.S. application Ser. No.12/273,483 filed Nov. 18, 2008, now issued U.S. Pat. No. 7,762,639 whichis a continuation of U.S. application Ser. No. 11/870,342 filed Oct. 10,2007, now issued U.S. Pat. No. 7,465,002, which is a continuation ofU.S. application Ser. No. 10/854,504 filed on 27 May 2004, now issuedU.S. Pat. No. 7,328,956, herein incorporated by reference.

FIELD OF THE INVENTION

The present invention relates to the field of printer controllers, whichreceive print data (usually from an external source such as a network orpersonal computer) and provide it to one or more printheads or otherprinting mechanisms.

The invention has primarily been developed for use in a pagewidth inkjetprinter in which considerable data processing and ordering is requiredof the printer controller, and will be described with reference to thisexample. However, it will be appreciated that the invention is notlimited to any particular type of printing technology, and may be usedin, for example, non-pagewidth and non-inkjet printing applications.

CO-PENDING APPLICATIONS

Various methods, systems and apparatus relating to the present inventionare disclosed in the following co-pending applications filed by theapplicant or assignee of the present invention with U.S. Pat. No.7,328,956:

7,374,266 7,427,117 7,448,707 7,281,330 10/854,503 7,328,956 7,735,9447,188,928 7,093,989 7,377,609 7,600,843 10/854,498 7,390,071 10/854,5267,549,715 7,607,757 7,267,417 10/854,505 7,517,036 7,275,805 7,314,2617,281,777 7,290,852 7,484,831 10/854,523 10/854,527 7,549,718 10/854,5207,631,190 7,557,941 10/854,499 10/854,501 7,266,661 7,243,193 10/854,518

The disclosures of these co-pending applications are incorporated hereinby cross-reference.

CROSS-REFERENCES

Various methods, systems and apparatus relating to the present inventionare disclosed in the following co-pending applications filed by theapplicant or assignee of the present invention. The disclosures of allof these co-pending applications are incorporated herein bycross-reference.

7,249,108 6,566,858 6,331,946 6,246,970 6,442,525 7,346,586 7,685,4236,374,354 7,246,098 6,816,968 6,757,832 6,334,190 6,745,331 7,249,1097,509,292 7,685,424 7,416,280 7,252,366 7,488,051 7,360,865 10/727,1627,377,608 7,399,043 7,121,639 7,165,824 7,152,942 10/727,157 7,181,5727,096,137 7,302,592 7,278,034 7,188,282 7,592,829 10/727,180 10/727,17910/727,192 10/727,274 7,707,621 7,523,111 7,573,301 7,660,998 10/754,53610/754,938 10/727,160 6,795,215 6,859,289 6,977,751 6,398,332 6,394,5736,622,923 6,747,760 6,921,144 7,454,617 7,194,629 10/791,792 7,182,2677,025,279 6,857,571 6,817,539 6,830,198 6,992,791 7,038,809 6,980,3237,148,992 7,139,091 6,947,173

BACKGROUND OF THE INVENTION

In a printhead module comprising a plurality of nozzles, there is alwaysthe possibility that a manufacturing defect, or over time in service,will cause one or more nozzle to fail. A failed nozzle can sometimes becorrected by error diffusion or color replacement. However, thesesolutions at best provide approximations of the color missing due to thedefective nozzle.

The chances of a nozzle defect increases at least linearly with thenumber of nozzles on the printhead module, both through the increase insample space for a failure to occur, and the reduction in nozzle sizewhich requires higher tolerances. Defective chips reduce yield, whichincreases the effective cost of the remaining chips. Nozzles that failin chips in service increase the costs of providing warranty cover.

It may also be desirable to reduce the rate at which nozzles fire inprinthead. This may be, for example, to reduce thermal problems or canbe the result of the desired nozzle fire rate exceeding the rate atwhich any given nozzle can fire.

The Applicant has designed a printhead that incorporates one or moreredundant rows of nozzles. It would be desirable to provide a printercontroller capable of providing data to such a printhead.

SUMMARY OF THE INVENTION

In a first aspect the present invention provides a printhead comprising:

-   1. A printer comprising:

at least one elongate printhead module comprising at least one row ofprinting nozzles; and

first and second printer controllers configured to process print datafor output to the printhead module, the first and second printercontrollers being connected to a common input of the printhead module.

-   Optionally, the printer comprises at least one synchronization means    between the first and second printer controllers for synchronizing    the output of data by the printer controllers.-   Optionally, the printer is configured such that the first and second    printer controllers sequentially output data to the common input.-   Optionally, the printer comprises two printhead modules, the printer    being configured such that: the first printer controller outputs    data to both printhead modules and the second printhead module; and    that the second printer controller outputs data to one of the    printhead modules.-   Optionally, the printhead modules are configured such that no data    passes between them.-   Optionally, each of the printer controllers is configurable to    supply the data to printhead modules of a plurality of different    lengths.-   Optionally, the printhead module comprises a pagewidth printhead.-   Optionally, the printhead module is capable of printing a maximum of    n of channels of print data and is configurable into:    -   a first mode, in which the printhead module is configured to        receive data for a first number of the channels; and    -   a second mode, in which the printhead module is configured to        receive print data for a second number of the channels, the        first number being greater than the second number; and

wherein the printer controllers are selectively configurable to outputdata for the first and second modes.

-   Optionally, the printer controllers are configured to receive print    data to be printed using at least two different inks and control    data for controlling printing of the print data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1. Single SoPEC A4 Simplex system

FIG. 2. Dual SoPEC A4 Simplex system

FIG. 3. Dual SoPEC A4 Duplex system

FIG. 4. Dual SoPEC A3 simplex system

FIG. 5. Quad SoPEC A3 duplex system

FIG. 6. SoPEC A4 Simplex system with extra SoPEC used as DRAM storage

FIG. 7. SoPEC A4 Simplex system with network connection to Host PC

FIG. 8. Document data flow

FIG. 9. Pages containing different numbers of bands

FIG. 10. Contents of a page band

FIG. 11. Page data path from host to SoPEC

FIG. 12. Page structure

FIG. 13. SoPEC System Top Level partition

FIG. 14. High level block diagram of DNC

FIG. 15. Dead nozzle table format

FIG. 16. Set of dots operated on for error diffusion

FIG. 17. Block diagram of DNC

FIG. 18. Printhead Nozzle Layout for conceptual 36 Nozzle AB singlesegment printhead

FIG. 19. Paper and printhead nozzles relationship (example with D₁=D₂=5)

FIG. 20. Dot line store logical representation

FIG. 21. Conceptual view of 2 adjacent printhead segments possible rowalignment

FIG. 22. Conceptual view of 2 adjacent printhead segments row alignment(as seen by the LLU)

FIG. 23. Paper and printhead nozzles relationship (example with D₁=D₂=5)

FIG. 24. Conceptual view of vertically misaligned printhead segment rows(external)

FIG. 25. Conceptual view of vertically misaligned printhead segment rows(internal)

FIG. 26. Conceptual view of color dependent vertically misalignedprinthead segment rows (internal)

FIG. 27. Conceptual horizontal misalignment between segments

FIG. 28. Relative positions of dot fired (example cases)

FIG. 29. PHI to linking printhead connection (Single SoPEC)

FIG. 30. PHI to linking printhead connection (2 SoPECs)

FIG. 31. CPU command word format

FIG. 32. Example data and command sequence on a print head channel

FIG. 33. PHI block partition

FIG. 34. Data generator state diagram

FIG. 35. PHI mode Controller

FIG. 36. Encoder RTL diagram

FIG. 37. 28-bit scrambler

FIG. 38. Printing with 1 SoPEC

FIG. 39. Printing with 2 SoPECs (existing hardware)

FIG. 40. Each SoPEC generates dot data and writes directly to a singleprinthead

FIG. 41. Each SoPEC generates dot data and writes directly to a singleprinthead

FIG. 42. Two SoPECs generate dots and transmit directly to the largerprinthead

FIG. 43. Serial Load

FIG. 44. Parallel Load

FIG. 45. Two SoPECs generate dot data but only one transmits directly tothe larger printhead

FIG. 46. Odd and Even nozzles on same shift register

FIG. 47. Odd and Even nozzles on different shift registers

FIG. 48. Interwoven shift registers

FIG. 49. Linking Printhead Concept

FIG. 50. Linking Printhead 30 ppm

FIG. 51. Linking Printhead 60 ppm

FIG. 52. Theoretical 2 tiles assembled as A-chip/A-chip—right angle join

FIG. 53. Two tiles assembled as A-chip/A-chip

FIG. 54. Magnification of color n in A-chip/A-chip

FIG. 55. A-chip/A-chip growing offset

FIG. 56. A-chip/A-chip aligned nozzles, sloped chip placement

FIG. 57. Placing multiple segments together

FIG. 58. Detail of a single segment in a multi-segment configuration

FIG. 59. Magnification of inter-slope compensation

FIG. 60. A-chip/B-chip

FIG. 61. A-chip/B-chip multi-segment printhead

FIG. 62. Two A-B-chips linked together

FIG. 63. Two A-B-chips with on-chip compensation

FIG. 64. SoPEC System top level partition

FIG. 65. Print construction and Nozzle position

FIG. 66. Conceptual horizontal misplacement between segments

FIG. 67. Printhead row positioning and default row firing order

FIG. 68. Firing order of fractionally misaligned segment

FIG. 69. Example of yaw in printhead IC misplacement

FIG. 70. Vertical nozzle spacing

FIG. 71. Single printhead chip plus connection to second chip

FIG. 72. Two printheads connected to form a larger printhead

FIG. 73. Colour arrangement.

FIG. 74. Nozzle Offset at Linking Ends

FIG. 75. Bonding Diagram

FIG. 76. MEMS Representation.

FIG. 77. Line Data Load and Firing, properly placed Printhead,

FIG. 78. Simple Fire order

FIG. 79. Micro positioning

FIG. 80. Measurement convention

FIG. 81. Scrambler implementation

FIG. 82. Block Diagram

FIG. 83. TDC block diagram

FIG. 84. DEX block diagram

DETAILED DESCRIPTION OF PREFERRED EMBODIMENT

A printhead having SoPEC ASICs (Small office home office Print EngineController) suitable for use in price sensitive SoHo printer products isprovided. The SoPEC ASIC is intended to be a relatively low costsolution for linking printhead control, replacing the multichipsolutions in larger more professional systems with a single chip. Theincreased cost competitiveness is achieved by integrating severalsystems such as a modified PEC1 printing pipeline, CPU control system,peripherals and memory sub-system onto one SoC ASIC, reducing componentcount and simplifying board design. SoPEC contains features making itsuitable for multifunction or “all-in-one” devices as well as dedicatedprinting systems.

Basic features of the preferred embodiment of SoPEC include:

-   -   Continuous 30 ppm operation for 1600 dpi output at A4/Letter.    -   Linearly scalable (multiple SoPECs) for increased print speed        and/or page width.    -   192 MHz internal system clock derived from low-speed crystal        input    -   PEP processing pipeline, supports up to 6 color channels at 1        dot per channel per clock cycle    -   Hardware color plane decompression, tag rendering, halftoning        and compositing    -   Data formatting for Linking Printhead    -   Flexible compensation for dead nozzles, printhead misalignment        etc.    -   Integrated 20 Mbit (2.5 MByte) DRAM for print data and CPU        program store    -   LEON SPARC v8 32-bit RISC CPU    -   Supervisor and user modes to support multi-threaded software and        security    -   1 kB each of I-cache and D-cache, both direct mapped, with        optimized 256-bit fast cache update.    -   1×USB2.0 device port and 3×USB2.0 host ports (including        integrated PHYs)    -   Support high speed (480 Mbit/sec) and full speed (12 Mbit/sec)        modes of USB2.0    -   Provide interface to host PC, other SoPECs, and external devices        e.g. digital camera    -   Enable alternative host PC interfaces e.g. via external        USB/ethernet bridge    -   Glueless high-speed serial LVDS interface to multiple Linking        Printhead chips    -   64 remappable GPIOs, selectable between combinations of        integrated system control components:    -   2×LSS interfaces for QA chip or serial EEPROM    -   LED drivers, sensor inputs, switch control outputs    -   Motor controllers for stepper and brushless DC motors    -   Microprogrammed multi-protocol media interface for scanner,        external RAM/Flash, etc.    -   112-bit unique ID plus 112-bit random number on each device,        combined for security protocol support    -   IBM Cu-11 0.13 micron CMOS process, 1.5V core supply, 3.3V IO.    -   208 pin Plastic Quad Flat Pack

The preferred embodiment linking printhead produces 1600 dpi bi-leveldots. On low-diffusion paper, each ejected drop forms a 22.5 m diameterdot. Dots are easily produced in isolation, allowing dispersed-dotdithering to be exploited to its fullest. Since the preferred form ofthe linking printhead is pagewidth and operates with a constant papervelocity, color planes are printed in good registration, allowingdot-on-dot printing. Dot-on-dot printing minimizes ‘muddying’ ofmidtones caused by inter-color bleed.

The SoPEC device can be used in several printer configurations andarchitectures. In the general sense, every preferred embodimentSoPEC-based printer architecture will contain:

-   -   One or more SoPEC devices.    -   One or more linking printheads.    -   Two or more LSS busses.    -   Two or more QA chips.    -   Connection to host, directly via USB2.0 or indirectly.    -   Connections between SoPECs (when multiple SoPECs are used).

The SoPEC device contains several system on a chip (SoC) components, aswell as the print engine pipeline control application specific logic.

The print engine pipeline (PEP) reads compressed page store data fromthe embedded memory, optionally decompresses the data and formats it forsending to the printhead. The print engine pipeline functionalityincludes expanding the page image, dithering the contone layer,compositing the black layer over the contone layer, rendering of Netpagetags, compensation for dead nozzles in the printhead, and sending theresultant image to the linking printhead.

SoPEC contains an embedded CPU for general-purpose system configurationand management. The CPU performs page and band header processing, motorcontrol and sensor monitoring (via the GPIO) and other system controlfunctions. The CPU can perform buffer management or report buffer statusto the host. The CPU can optionally run vendor application specific codefor general print control such as paper ready monitoring and LED statusupdate.

The printhead is constructed by abutting a number of printhead ICstogether. Each SoPEC can drive up to 12 printhead ICs at data rates upto 30 ppm or 6 printhead ICs at data rates up to 60 ppm. For higher datarates, or wider printheads, multiple SoPECs must be used.

In a multi-SoPEC system, the primary communication channel is from aUSB2.0 Host port on one SoPEC (the ISCMaster), to the USB2.0 Device portof each of the other SoPECs (ISCSlaves). If there are more ISCSlaveSoPECs than available USB Host ports on the ISCMaster, additionalconnections could be via a USB Hub chip, or daisy-chained SoPEC chips.Typically one or more of SoPEC's GPIO signals would also be used tocommunicate specific events between multiple SoPECs.

In FIG. 1, a single SoPEC device is used to control a linking printheadwith 11 printhead ICs. The SoPEC receives compressed data from the hostthrough its USB device port. The compressed data is processed andtransferred to the printhead. This arrangement is limited to a speed of30 ppm. The single SoPEC also controls all printer components such asmotors, LEDs, buttons etc, either directly or indirectly.

In FIG. 2, two SoPECs control a single linking printhead, to provide 60ppm A4 printing. Each SoPEC drives 5 or 6 of the printheads ICs thatmake up the complete printhead. SoPEC #0 is the ISCMaster, SoPEC #1 isan ISCSlave. The ISCMaster receives all the compressed page data forboth SoPECs and re-distributes the compressed data for the ISCSlave overa local USB bus. There is a total of 4 MBytes of page store memoryavailable if required. Note that, if each page has 2 MBytes ofcompressed data, the USB2.0 interface to the host needs to run in highspeed (not full speed) mode to sustain 60 ppm printing. (In practice,many compressed pages will be much smaller than 2 MBytes). The controlof printer components such as motors, LEDs, buttons etc, is sharedbetween the 2 SoPECs in this configuration.

In FIG. 3, two SoPEC devices are used to control two printheads. Eachprinthead prints to opposite sides of the same page to achieve duplexprinting. SoPEC #0 is the ISCMaster, SoPEC #1 is an ISCSlave. TheISCMaster receives all the compressed page data for both SoPECs andre-distributes the compressed data for the ISCSlave over a local USBbus. This configuration could print 30 double-sided pages per minute.

In FIG. 4, two SoPEC devices are used to control one A3 linkingprinthead, constructed from 16 printhead ICs. Each SoPEC controls 8printhead ICs. This system operates in a similar manner to the 60 ppm A4system in FIG. 2, although the speed is limited to 30 ppm at A3, sinceeach SoPEC can only drive 6 printhead ICs at 60 ppm speeds. A total of 4Mbyte of page store is available, this allows the system to usecompression rates as in a single SoPEC A4 architecture, but with theincreased page size of A3.

In FIG. 5 a four SoPEC system is shown. It contains 2 A3 linkingprintheads, one for each side of an A3 page. Each printhead contain 16printhead ICs, each SoPEC controls 8 printhead ICs. SoPEC #0 is theISCMaster with the other SoPECs as ISCSlaves. Note that all 3 USB Hostports on SoPEC #0 are used to communicate with the 3 ISCSlave SoPECs. Intotal, the system contains 8 Mbytes of compressed page store (2 Mbytesper SoPEC), so the increased page size does not degrade the system printquality, from that of an A4 simplex printer. The ISCMaster receives allthe compressed page data for all SoPECs and re-distributes thecompressed data over the local USB bus to the ISCSlaves. Thisconfiguration could print 30 double-sided A3 sheets per minute.

Extra SoPECs can be used for DRAM storage e.g. in FIG. 6 an A4 simplexprinter can be built with a single extra SoPEC used for DRAM storage.The DRAM SoPEC can provide guaranteed bandwidth delivery of data to theprinting SoPEC. SoPEC configurations can have multiple extra SoPECs usedfor DRAM storage.

The Host PC rasterizes and compresses the incoming document on a page bypage basis. The page is restructured into bands with one or more bandsused to construct a page. The compressed data is then transferred to theSoPEC device directly via a USB link, or via an external bridge e.g.from ethernet to USB. A complete band is stored in SoPEC embeddedmemory. Once the band transfer is complete the SoPEC device reads thecompressed data, expands the band, normalizes contone, bi-level and tagdata to 1600 dpi and transfers the resultant calculated dots to thelinking printhead.

The document data flow is

-   -   The RIP software rasterizes each page description and compress        the rasterized page image.    -   The infrared layer of the printed page optionally contains        encoded Netpage tags at a programmable density.    -   The compressed page image is transferred to the SoPEC device via        the USB (or ethernet), normally on a band by band basis.    -   The print engine takes the compressed page image and starts the        page expansion.    -   The first stage page expansion consists of 3 operations        performed in parallel    -   expansion of the JPEG-compressed contone layer    -   expansion of the SMG4 fax compressed bi-level layer    -   encoding and rendering of the bi-level tag data.    -   The second stage dithers the contone layer using a programmable        dither matrix, producing up to four bi-level layers at        full-resolution.    -   The third stage then composites the bi-level tag data layer, the        bi-level SMG4 fax de-compressed layer and up to four bi-level        JPEG de-compressed layers into the full-resolution page image.    -   A fixative layer is also generated as required.    -   The last stage formats and prints the bi-level data through the        linking printhead via the printhead interface.

The SoPEC device can print a full resolution page with 6 color planes.Each of the color planes can be generated from compressed data throughany channel (either JPEG compressed, bi-level SMG4 fax compressed, tagdata generated, or fixative channel created) with a maximum number of 6data channels from page RIP to linking printhead color planes.

The mapping of data channels to color planes is programmable. Thisallows for multiple color planes in the printhead to map to the samedata channel to provide for redundancy in the printhead to assist deadnozzle compensation.

Also a data channel could be used to gate data from another datachannel. For example in stencil mode, data from the bilevel data channelat 1600 dpi can be used to filter the contone data channel at 320 dpi,giving the effect of 1600 dpi edged contone images, such as 1600 dpicolor text.

The SoPEC is a page rendering engine ASIC that takes compressed pageimages as input, and produces decompressed page images at up to 6channels of bi-level dot data as output. The bi-level dot data isgenerated for the Memjet linking printhead. The dot generation processtakes account of printhead construction, dead nozzles, and allows forfixative generation.

A single SoPEC can control up to 12 linking printheads and up to 6 colorchannels at >10,000 lines/sec, equating to 30 pages per minute. A singleSoPEC can perform full-bleed printing of A4 and Letter pages. The 6channels of colored ink are the expected maximum in a consumer SOHO, oroffice Memjet printing environment:

-   -   CMY, for regular color printing.    -   K, for black text, line graphics and gray-scale printing.    -   IR (infrared), for Netpage-enabled applications.    -   F (fixative), to enable printing at high speed. Because the        Memjet printer is capable of printing so fast, a fixative may be        required on specific media types (such as calendared paper) to        enable the ink to dry before the page touches a previously        printed page. Otherwise the pages may bleed on each other. In        low speed printing environments, and for plain and photo paper,        the fixative is not be required.

SoPEC is color space agnostic. Although it can accept contone data asCMYX or RGBX, where X is an optional 4th channel (such as black), italso can accept contone data in any print color space. Additionally,SoPEC provides a mechanism for arbitrary mapping of input channels tooutput channels, including combining dots for ink optimization,generation of channels based on any number of other channels etc.However, inputs are typically CMYK for contone input, K for the bi-levelinput, and the optional Netpage tag dots are typically rendered to aninfra-red layer. A fixative channel is typically only generated for fastprinting applications.

SoPEC is resolution agnostic. It merely provides a mapping between inputresolutions and output resolutions by means of scale factors. Theexpected output resolution is 1600 dpi, but SoPEC actually has noknowledge of the physical resolution of the linking printhead.

SoPEC is page-length agnostic. Successive pages are typically split intobands and downloaded into the page store as each band of information isconsumed and becomes free. SoPEC provides mechanisms for synchronizationwith other SoPECs. This allows simple multi-SoPEC solutions forsimultaneous A3/A4/Letter duplex printing. However, SoPEC is alsocapable of printing only a portion of a page image. Combiningsynchronization functionality with partial page rendering allowsmultiple SoPECs to be readily combined for alternative printingrequirements including simultaneous duplex printing and wide formatprinting.

From the highest point of view the SoPEC device consists of 3 distinctsubsystems

-   -   CPU Subsystem    -   DRAM Subsystem    -   Print Engine Pipeline (PEP) Subsystem        See FIG. 13 for a block level diagram of SoPEC.

The CPU subsystem controls and configures all aspects of the othersubsystems. It provides general support for interfacing andsynchronising the external printer with the internal print engine. Italso controls the low speed communication to the QA chips. The CPUsubsystem contains various peripherals to aid the CPU, such as GPIO(includes motor control), interrupt controller, LSS Master, MMI andgeneral timers. The CPR block provides a mechanism for the CPU topowerdown and reset individual sections of SoPEC. The UDU and UHUprovide high-speed USB2.0 interfaces to the host, other SoPEC devices,and other external devices. For security, the CPU supports user andsupervisor mode operation, while the CPU subsystem contains somededicated security components.

The DRAM subsystem accepts requests from the CPU, UHU, UDU, MMI andblocks within the PEP subsystem. The DRAM subsystem (in particular theDIU) arbitrates the various requests and determines which request shouldwin access to the DRAM. The DIU arbitrates based on configuredparameters, to allow sufficient access to DRAM for all requestors. TheDIU also hides the implementation specifics of the DRAM such as pagesize, number of banks, refresh rates etc.

The PEP subsystem accepts compressed pages from DRAM and renders them tobi-level dots for a given print line destined for a printhead interfacethat communicates directly with up to 12 linking printhead ICs.

The first stage of the page expansion pipeline is the CDU, LBD and TE.The CDU expands the JPEG-compressed contone (typically CMYK) layer, theLBD expands the compressed bi-level layer (typically K), and the TEencodes Netpage tags for later rendering (typically in IR, Y or K ink).The output from the first stage is a set of buffers: the CFU, SFU, andTFU. The CFU and SFU buffers are implemented in DRAM.

The second stage is the HCU, which dithers the contone layer, andcomposites position tags and the bi-level spot0 layer over the resultingbi-level dithered layer. A number of options exist for the way in whichcompositing occurs. Up to 6 channels of bi-level data are produced fromthis stage. Note that not all 6 channels may be present on theprinthead. For example, the printhead may be CMY only, with K pushedinto the CMY channels and IR ignored. Alternatively, the position tagsmay be printed in K or Y if IR ink is not available (or for testingpurposes).

The third stage (DNC) compensates for dead nozzles in the printhead bycolor redundancy and error diffusing dead nozzle data into surroundingdots.

The resultant bi-level 6 channel dot-data (typically CMYK-IRF) isbuffered and written out to a set of line buffers stored in DRAM via theDWU.

Finally, the dot-data is loaded back from DRAM, and passed to theprinthead interface via a dot FIFO. The dot FIFO accepts data from theLLU up to 2 dots per system clock cycle, while the PHI removes data fromthe FIFO and sends it to the printhead at a maximum rate of 1.5 dots persystem clock cycle.

SoPEC must address

-   -   20 Mbit DRAM.    -   PCU addressed registers in PEP.    -   CPU-subsystem addressed registers.        SoPEC has a unified address space with the CPU capable of        addressing all CPU-subsystem and PCU-bus accessible registers        (in PEP) and all locations in DRAM. The CPU generates        byte-aligned addresses for the whole of SoPEC. 22 bits are        sufficient to byte address the whole SoPEC address space.

The embedded DRAM is composed of 256-bit words. Since the CPU-subsystemmay need to write individual bytes of DRAM, the DIU is byte addressable.22 bits are required to byte address 20 Mbits of DRAM.

Most blocks read or write 256-bit words of DRAM. For these blocks onlythe top 17 bits i.e. bits 21 to 5 are required to address 256-bit wordaligned locations.

The exceptions are

-   -   CDU which can write 64-bits so only the top 19 address bits i.e.        bits 21-3 are required.    -   The CPU-subsystem always generates a 22-bit byte-aligned DIU        address but it will send flags to the DIU indicating whether it        is an 8, 16 or 32-bit write.    -   The UHU and UDU generate 256-bit aligned addresses, with a        byte-wise write mask associated with each data word, to allow        effective byte addressing of the DRAM.        Regardless of the size no DIU access is allowed to span a        256-bit aligned DRAM word boundary.

PEP Unit configuration registers which specify DRAM locations shouldspecify 256-bit aligned DRAM addresses i.e. using address bits 21:5.Legacy blocks from PEC1 e.g. the LBD and TE may need to specify 64-bitaligned DRAM addresses if these reused blocks DRAM addressing isdifficult to modify. These 64-bit aligned addresses require address bits21:3. However, these 64-bit aligned addresses should be programmed tostart at a 256-bit DRAM word boundary. Unlike PEC1, there are noconstraints in SoPEC on data organization in DRAM except that all datastructures must start on a 256-bit DRAM boundary. If data stored is nota multiple of 256-bits then the last word should be padded.

The CPU subsystem bus supports 32-bit word aligned read and writeaccesses with variable access timings. The CPU subsystem bus does notcurrently support byte reads and writes.

The Dead Nozzle Compensator (DNC) is responsible for adjusting Memjetdot data to take account of non-functioning nozzles in the Memjetprinthead. Input dot data is supplied from the HCU, and the correcteddot data is passed out to the DWU. The high level data path is shown bythe block diagram in FIG. 14.

The DNC compensates for a dead nozzles by performing the followingoperations:

-   -   Dead nozzle removal, i.e. turn the nozzle off    -   Ink replacement by direct substitution e.g. K->K_(alternative)    -   Ink replacement by indirect substitution e.g. K->CMY    -   Error diffusion to adjacent nozzles    -   Fixative corrections

The DNC is required to efficiently support up to 5% dead nozzles, underthe expected DRAM bandwidth allocation, with no restriction on wheredead nozzles are located and handle any fixative correction due tonozzle compensations. Performance must degrade gracefully after 5% deadnozzles.

Dead nozzles are identified by means of a position value and a maskvalue. Position information is represented by a 10-bit delta encodedformat, where the 10-bit value defines the number of dots between deadnozzle columns. The delta information is stored with an associated 6-bitdead nozzle mask (dn_mask) for the defined dead nozzle position. Eachbit in the dn_mask corresponds to an ink plane. A set bit indicates thatthe nozzle for the corresponding ink plane is dead. The dead nozzletable format is shown in FIG. 15. The DNC reads dead nozzle informationfrom DRAM in single 256-bit accesses. A 10-bit delta encoding scheme ischosen so that each table entry is 16 bits wide, and 16 entries fitexactly in each 256-bit read. Using 10-bit delta encoding means that themaximum distance between dead nozzle columns is 1023 dots. It ispossible that dead nozzles may be spaced further than 1023 dots fromeach other, so a null dead nozzle identifier is required. A null deadnozzle identifier is defined as a 6-bit dn_mask of all zeros. These nulldead nozzle identifiers should also be used so that:

-   -   the dead nozzle table is a multiple of 16 entries (so that it is        aligned to the 256-bit DRAM locations)    -   the dead nozzle table spans the complete length of the line,        i.e. the first entry dead nozzle table should have a delta from        the first nozzle column in a line and the last entry in the dead        nozzle table should correspond to the last nozzle column in a        line.

Note that the DNC deals with the width of a page. This may or may not bethe same as the width of the printhead (printhead ICs may overlap due tomisalignment during assembly, and additionally, the LLU may introducemargining to the page). Care must be taken when programming the deadnozzle table so that dead nozzle positions are correctly specified withrespect to the page and printhead.

Due to construction limitations of the printhead it is possible thatnozzle rows within a printhead segment may be misaligned relative toeach other by up to 5 dots per half line, which means 56 dot positionsover 12 half lines (i.e. 28 dot pairs). Vertical misalignment can alsooccur but is compensated for in the LLU and not considered here. The DWUis required to compensate for the horizontal misalignment.

Dot data from the HCU (through the DNC) produces a dot of 6 colors alldestined for the same physical location on paper. If the nozzle rows inthe within a printhead segment are aligned as shown in FIG. 18 then noadjustment of the dot data is needed.

A conceptual misaligned printhead is shown in FIG. 21. The exact shapeof the row alignment is arbitrary, although is most likely to be sloping(if sloping, it could be sloping in either direction).

The DWU is required to adjust the shape of the dot streams to take intoaccount the relative horizontal displacement of nozzles rows between 2adjacent printhead segments. The LLU compensates for the vertical skewbetween printhead segments, and the vertical and horizontal skew withinprinthead segments. The nozzle row skew function aligns rows tocompensate for the seam between printhead segments (as shown in FIG. 21)and not for the seam within a printhead (as shown in FIG. 18). The DWUnozzle row function results in aligned rows as shown in the example inFIG. 22.

To insert the shape of the skew into the dot stream, for each line wemust first insert the dots for non-printable area 1, then the printablearea data (from the DNC), and then finally the dots for non-printablearea 2. This can also be considered as: first produce the dots fornon-printable area 1 for line n, and then a repetition of:

-   -   produce the dots for the printable area for line n (from the        DNC)    -   produce the dots for the non-printable area 2 (for line n)        followed by the dots of non-printable area 1 (for line n+1)

The reason for considering the problem this way is that regardless ofthe shape of the skew, the shape of non-printable area 2 merged with theshape of non-printable area 1 will always be a rectangle since thewidths of non-printable areas 1 and 2 are identical and the lengths ofeach row are identical. Hence step 2 can be accomplished by simplyinserting a constant number (NozzleSkewPadding) of 0 dots into thestream.

For example, if the color n even row non-printable area 1 is of lengthX, then the length of color n even row non-printable area 2 will be oflength NozzleSkewPadding−X. The split between non-printable areas 1 and2 is defined by the NozzleSkew registers. Data from the DNC is destinedfor the printable area only, the DWU must generate the data destined forthe non-printable areas, and insert DNC dot data correctly into the dotdata stream before writing dot data to the fifos. The DWU inserts theshape of the misalignment into the dot stream by delaying dot datadestined to different nozzle rows by the relative misalignment skewamount.

The Printhead interface (PHI) accepts dot data from the LLU andtransmits the dot data to the printhead, using the printhead interfacemechanism. The PHI generates the control and timing signals necessary toload and drive the printhead. A printhead is constructed from a numberof printhead segments. The PHI has 6 transmission lines (printheadchannel), each line is capable of driving up to 2 printhead segments,allowing a single PHI to drive up to 12 printhead segments. The PHI iscapable of driving any combination of 0, 1 or 2 segments on anyprinthead channel.

The PHI generates control information for transmission to each printheadsegment. The control information can be generated automatically by thePHI based on configured values, or can be constructed by the CPU for thePHI to insert into the data stream.

The PHI transmits data to printhead segments at a rate of 288 Mhz, over6 LVDS data lines synchronous to 2 clocks. Both clocks are in phase witheach other. In order to assist sampling of data in the printheadsegments, each data line is encoded with 8b10b encoding, to minimize themaximum number of bits without a transition. Each data line requires acontinuous stream of symbols, if a data line has no data to send it mustinsert IDLE symbols to enable the receiving printhead to remainsynchronized. The data is also scrambled to reduce EMI effects due tolong sequences of identical data sent to the printhead segment (i.e.IDLE symbols between lines). The descrambler also has the added benefitin the receiver of increasing the chance single bit errors will be seenmultiple times. The 28-bit scrambler is self-synchronizing with afeedback polynomial of 1+x¹⁵+x²⁸.

The PHI needs to send control commands to each printhead segment as partof the normal line and page download to each printhead segment. Thecontrol commands indicate line position, color row information, fireperiod, line sync pulses etc. to the printhead segments.

A control command consists of one control symbol, followed by 0 or moredata or control symbols. A data or control symbol is defined as a 9-bitunencoded word. A data symbol has bit 8 set to 0, the remaining 8 bitsrepresent the data character. A control symbol has bit 8 set to 1, withthe 8 remaining bits set to a limited set of other values to completethe 8b10b code set.

Each command is defined by CmdCfg[CMD_NAME] register. The commandconfiguration register configures 2 pointers into a symbol array(currently the symbol array is 32 words, but could be extended). Bits4:0 of the command configuration register indicate the start symbol, andbits 9:5 indicate the end symbol. Bit 10 is the empty string bit and isused to indicate that the command is empty, when set the command isignored and no symbols are sent. When a command is transmitted to aprinthead segment, the symbol pointed to by the start pointer is sendfirst, then the start pointer +1 etc. and all symbols to the end symbolpointer. If the end symbol pointer is less than the start symbol pointerthe PHI will send all symbols from start to stop wrapping at 32.

The IDLE command is configured differently to the others. It is alwaysonly one symbol in length and cannot be configured to be empty. The IDLEsymbol value is defined by the IdleCmdCfg register.

The symbol array can be programmed by accessing the SymbolTableregisters. Note that the symbol table can be written to at any time, butcan only be read when Go is set to 0.

The PHI provides a mechanism for the CPU to send data and control wordsto any individual segment or to broadcast to all segmentssimultaneously. The CPU writes commands to the command FIFO, and the PHIaccepts data from the command FIFO, and transmits the symbols to theaddressed printhead segment, or broadcasts the symbols to all printheadsegments.

The PHI operates in 2 modes, CPU command mode and data mode. A CPUcommand always has higher priority than the data stream (or a stream ofidles) for transmission to the printhead. When there is data in thecommand FIFO, the PHI will change to CPU command mode as soon aspossible and start transmitting the command word. If the PHI detectsdata in the command FIFO, and the PHI is in the process of transmittinga control word the PHI waits for the control word to complete and thenswitches to CPU command mode. Note that idles are not considered controlwords. The PHI will remain in CPU command mode until it encounters acommand word with the EOC flag set and no other data in the commandFIFO.

The PHI must accept data for all printhead channels from the LLUtogether, and transmit all data to all printhead segments together. Ifthe CPU command FIFO wants to send data to a particular printheadsegment, the PHI must stall all data channels from the LLU, and sendIDLE symbols to all other print channels not addressed by the CPUcommand word. If the PHI enters CPU command mode and begins to transmitcommand words, and the command FIFO becomes empty but the PHI has notencountered an EOC flag then the PHI will continue to stall the LLU andinsert IDLE symbols into the print streams. The PHI remains in CPUcommand mode until an EOC flag is encountered. To prevent such stallingthe command FIFO has an enable bit CmdFIFOEnable which enables the PHIreading the command FIFO. It allows the CPU to write several words tothe command FIFO without the PHI beginning to read the FIFO. If the CPUdisables the FIFO (setting CmdFIFOEnable to 0) and the PHI is currentlyin CPU command mode, the PHI will continue transmitting the CPU commanduntil it encounters an EOC flag and will then disable the FIFO.

When the PHI is switching from CPU command mode to data transfer mode,it sends a RESUME command to the printhead channel group data transferthat was interrupted. This enables each printhead to easilydifferentiate between control and data streams. For example if the PHIis transmitting data to printhead group B and is interrupted to transmita CPU command, then upon return to data mode the PHI must send aRESUME_B control command. If the PHI was between pages (when Go=0)transmitting IDLE commands and was interrupted by a CPU command, itdoesn't need to send any resume command before returning to transmitIDLE.

The command FIFO can be written to at any time by the CPU by writing tothe CmdFifo register. The CmdFiFO register allows FIFO style access tothe command FIFO. Writing to the CmdFIFO register will write data to thecommand FIFO address pointed to by the write pointer and will incrementthe write pointer. The CmdFIFO register can be read at any time but willalways return the command FIFO value pointed to by the internal readpointer. The current fill level of the CPU command FIFO can be read byaccessing the CmdFIFOLevel register. The command FIFO is 32 words×14bits.

The PHI synchronizes line data transmission with sync pulses generatedby the GPIO block (which in turn could be synchronized to the GPIO blockin another SoPEC). The PHI waits for a line sync pulse and thentransmits line data and the FIRE command to all printhead segments.

It is possible that when a line sync pulse arrives at the PHI that notall the data has finished being sent to the printheads. If the PHI wereto forward this signal on then it would result in an incorrect print ofthat line, which is an error condition. This would indicate a bufferunderflow in PEC1.

However, in SoPEC the printhead segments can only receive line syncsignals from the SoPEC providing them data. Thus it is possible that thePHI could delay in sending the line sync pulse until it had finishedproviding data to the printhead. The effect of this would be a line thatis printed slightly after where it should be printed. In a single SoPECsystem this effect would probably not be noticeable, since all printheadsegments would have undergone the same delay. In a multi-SoPEC systemdelays would cause a difference in the location of the lines, if thedelay was great this may be noticeable.

If a line sync is early the PHI records it as a pending line sync andwill send the corresponding next line and FIRE command at the nextavailable time (i.e. when the current line of data is finishedtransferring to the printhead). It is possible that there may bemultiple pending line syncs, whether or not this is an error conditionis printer specific. The PHI records all pending line syncs(LineSyncPend register), and if the level of pending lines syncs risesover a configured level (LineSyncMaxPend register) the PHI will set theMaxSyncPend bit in the PhiStatus register which if enabled can cause aninterrupt. The CPU interrupt service routine can then evaluate theappropriate response, which could involve halting the PHI.

The PHI also has 2 print speed limitation mechanisms. The LineTimeMinregister specifies the minimum line time period in pclk cycles and theDynLineTimeMin register which also specifies the minimum line timeperiod in pclk cycles but is updated dynamically after each FIRE commandis transmitted. The PHI calculates DynLineTimeCalcMin value based on thelast line sync period adjusted by a scale factor specified by theDynLineTimeMinScaleNum register. When a FIRE command is transmitted tothe printhead the PHI moves the DynLineTimeCalcMin to the DynLineTimeMinregister to limit the next line time. The DynLineTimeCalcMin value isupdated for each new line sync (same as the FirePeriodCalc) whereas theDynLineTimeMin register is updated when a FIRE command is transmitted tothe printhead (same as the FirePeriod register). The dynamic minimumline time is intended to ensure the previous calculated fire period willhave sufficient time to fire a complete line before the PHI beginssending the next line of data.

The scale factor is defined as the ratio of the DynLineTimeMinScaleNumnumerator value to a fixed denominator value of 0x10000, allowing amaximum scale factor of 1. The PHI also provides a mechanism where itcan generate an interrupt to the ICU (phi_icu_line_irq) after a fixednumber of line syncs are received or a fixed number of FIRE commands aresent to the printhead. The LineInterrupt register specifies the numberof line syncs (or FIRE commands) to count before the interrupt isgenerated and the LineInterruptSrc register selects if the count shouldbe line syncs or FIRE commands.

The PHI sends data to each printhead segment in a fixed order insertingthe appropriate control command sequences into the data stream at thecorrect time. The PHI receives a fixed data stream from the LLU, it isthe responsibility of the PHI to determine which data is destined forwhich line, color nozzle row and printhead segment, and to insert thecorrect command sequences.

The SegWidth register specifies the number of dot pairs per half colornozzle row. To avoid padding to the nearest 8 bits (data symbol inputamount) the SegWidth must be programmed to a multiple of 8. The MaxColorregister specifies the number of half nozzle rows per printhead segment.The MaxSegment specifies the maximum number segments per printheadchannel. If MaxSegment is set to 0 then all enabled channels willgenerate a data stream for one segment only. If MaxSegment is set to 1then all enabled channels will generate data for 2 segments. The LLUwill generate null data for any missing printhead segments.

The PageLenLine register specifies the number of lines of data to acceptfrom the LLU and transfer to the printhead before setting the pagefinished flag (PhiPageFinish) in the PhiStatus register.

Printhead segments are divided into 2 groups, group A segments are 0, 2,4, 6, 8, 10 and group B segments are 1, 3, 5, 7, 9, 11. For anyprinthead channel, group A segment data is transmitted first then groupB.

Each time a line sync is received from the GPIO, the PHI sends a line ofdata and a fire (FIRE) command to all printhead segments. The PHI firstsends a next color command (NC A) for the first half color nozzle rowfollowed by nozzle data for the first half color dots. The number ofdots transmitted (and accepted from the LLU) is configured by SegWidthregister. The PHI then sends a next color command indicating to theprinthead to reconfigure to accept the next color nozzle data. The PHIthen sends the next half color dots. The process is repeated forMaxColor number of half nozzle rows. After all dots for a particularsegment are transmitted, the PHI sends a next color B (NC_B) command toindicate to the group B printheads to prepare to accept nozzle row data.The command and data sequence is repeated as before. The linetransmission to the printhead is completed with the transmission of aFIRE command.

The PHI can optionally insert a number of IDLE symbols before each nextcolor command. The number of IDLE symbols inserted is configured by theIdleInsert register. If it's set to zero no symbols will be inserted.

When a line is complete, the PHI decrements the PageLenLine counter, andwaits for the next line sync pulse from the GPIO before beginning thenext line of data. The PHI continues sending line data until thePageLenLine counter is 0 indicating the last line. When the last line istransmitted to the printhead segments, the PHI sets a page finished flag(PhiPageFinish) in the PhiStatus register. The PHI will then wait untilthe Go bit is toggled before sending the next page to the printhead.

Before starting printing SoPEC must configure the printhead segments. Ifthere is more than one printhead segment on a printline, the printheadsegments must be assigned a unique ID per print line. The IDs areassigned by holding one group of segments in reset while the other groupis programmed by a CPU command stream issued through the PHI. The PHIdoes not directly control the printhead reset lines. They are connectedto CPR block output pins and are controlled by the CPU through the CPR.

The printhead also provides a mechanism for reading data back from eachindividual printhead segment. All printhead segments use a common databack channel, so only one printhead segment can send data at a time.SoPEC issues a CPU command stream directed at a particular printheadsegment, which causes the segment to return data on the back channel.The back channel is connected to a GPIO input, and is sampled by the CPUthrough the GPIO.

If SoPEC is being used in a multi-SoPEC printing system, it is possiblethat not all print channels, or clock outputs are being used. Any unuseddata outputs can be disabled by programming the PhiDataEnable register,or unused clock outputs disabled by programming the PhiClkEnable.

The CPU when enabling or disabling the clock or data outputs must ensurethat the printhead segments they are connected to are held in a benignstate while toggling the enable status of the output pins.

The PHI calculates the fire period needed in the printhead segmentsbased on the last line sync period, adjusted by a fractional amount. Thefractional factor is dependant on the way the columns in the printheadare grouped, the particular clock used within the printhead to countthis period and the proportion of a line time over which the nozzles forthat line must be fired. For example, one current plan has fire groupsconsisting of 32 nozzle columns which are physically located in a waythat require them to be fired over a period of around 96% of the linetime. A count is needed to indicate a period of (linetime/32)*96% for a144 MHz clock.

The fractional amount the fire period is adjusted by is configured bythe FireScaleNum register. The scale factor is the ratio of theconfigurable FireScaleNum numerator register and a fixed denominator of0x10000. Note that the fire period is calculated in the pclk domain, butis used in the phiclk domain. The fractional registers will need to beprogrammed to take account of the ratio of the pclk and phiclkfrequencies.

A new fire period is calculated with every new line sync pulse from theGPIO, regardless of whether the line sync pulse results in a new line ofdata being send to the printhead segments, or the line sync pendinglevel. The latest calculated fire period by can read by accessing theFirePeriodCalc register.

The PHI transfers the last calculated fire period value (FirePeriodCalc)to the FirePeriod register immediately before the FIRE command is sentto the printhead. This prevents the FirePeriod value getting updatedduring the transfer of a FIRE command to the printhead, possibly sendingan incorrect fire period value to the printhead.

The PHI can optionally send the calculated fire period by placing METAcharacter symbols in a command stream (either a CPU command, or acommand configured in the command table). The META symbols are detectedby the PHI and replaced with the calculated fire period.

Immediately after the PHI leaves its reset it will start sending IDLEcommands to all printhead data channels. The PHI will not accept anydata from the LLU until the Go bit is set. Note the command table can beprogrammed at any time but cannot be used by the internal PHY when Go is0.

When Go is set to 1 the PHI will accept data from the LLU. When dataactually arrives in the data buffer the PHI will set the PhiDataReadybit in the PhiStatus register. The PHI will not start sending data tothe printhead until it receives 2 line syncs from the GPIO(gpio_phi_line_sync). The PHI needs to wait for 2 line syncs to allow itto calculate the fire period value. The first line sync will not becomepending, and will not result in a corresponding FIRE command. Note thatthe PHI does not need to wait for data from the LLU before it cancalculate the fire period. If the PHI is waiting for data from the LLUany line syncs it receives from the GPIO (except the first one) willbecome pending.

Once data is available and the fire period is calculated the PHI willstart producing print streams. For each line transmitted the PHI willwait for a line sync pulse (or the minimum line time if a line sync ispending) before sending the next line of data to the printheads. The PHIcontinues until a full page of data has been transmitted to theprinthead (as specified by the PageLenLine register). When the page iscomplete the PHI will automatically clear the Go bit and will set thePhiPageFinish flag in the PhiStatus register. Any bit in the PhiStatusregister can be used to generate an interrupt to the ICU.

A bi-lithic printhead (as distinct from the linking printhead) is nowdescribed from the point of view of printing 30 ppm from a SoPEC ASIC,as well as architectures that solve the 60 ppm printing requirementusing the bi-lithic printhead model.

To print at 30 ppm, the printheads must print a single page within 2seconds. This would include the time taken to print the page itself plusany inter-page gap (so that the 30 ppm target could be met). Therequired printing rate assumes an inter-sheet spacing of 4 cm.

A baseline SoPEC system connecting to two printhead segments is shown inFIG. 38. The two segments (A and B) combine to form a printhead oftypical width 13,824 nozzles per color. A single SoPEC produces the datafor both printheads for the entire page. Therefore it has the entireline time in which to generate the dot data.

A Letter page is 11 inches high. Assuming 1600 dpi and a 4 cm inter-pagegap, there are 20,120 lines. This is a line rate of 10.06 KHz (a linetime of 99.4 us). The printhead is 14,080 dots wide. To calculate thesedots within the line time, SoPEC requires a 140.8 MHz dot generationrate. Since SoPEC is run at 160 MHz and generates 1 dot per cycle, it isable to meet the Letter page requirement and cope with a small amount ofstalling during the dot generation process.

An A4 page is 297 mm high. Assuming 62.5 dots/mm and a 4 cm inter-pagegap, there are 21,063 lines. This is a line rate of 10.54 KHz (a linetime of 94.8 us). The printhead is 14,080 dots wide. To calculate thesedots within the line time, SoPEC requires a 148.5 MHz dot generationrate. Since SoPEC is run at 160 MHz and generates 1 dot per cycle, it isable to meet the A4 page requirement and cope with minimal stalling.

Assuming an n-color printhead, SoPEC must transmit 14,080 dots n-bitswithin the line time. i.e. n the data generation rate=n-bits 14,080 dots10.54 KHz. Thus a 6-color printhead requires 874.2 Mb/sec. Thetransmission time is further constrained by the fact that no data mustbe transmitted to the printhead segments during a window around thelinesync pulse. Assuming a 1% overhead for linesync overhead (being veryconservative), the required transmission bandwidth for 6 colors is 883Mb/sec.

However, the data is transferred to both segments simultaneously. Thismeans the longest time to transfer data for a line is determined by thetime to transfer print data to the longest print segment. There are 9744nozzles per color across a type7 printhead. We therefore must be capableof transmitting 6-bits 9744 dots at the line rate i.e. 6-bits 9744 10.54KHz=616.2 Mb/sec. Again, assuming a 1% overhead for linesync overhead,the required transmission bandwidth to each printhead is 622.4 Mb/sec.

The connections from SoPEC to each segment consist of 2 1-bit data linesthat operate at 320 MHz each. This gives a total of 640 Mb/sec.Therefore the dot data can be transmitted at the appropriate rate to theprinthead to meet the 30 ppm requirement.

SoPEC has a dot generation pipeline that generates 1 6-color dot percycle. The LBD and TE are imported blocks from PEC1, with only marginalchanges, and these are therefore capable of nominally generating 2 dotsper cycle. However the rest of the pipeline is only capable ofgenerating 1 dot per cycle.

SoPEC is capable of transmitting data to 2 printheads simultaneously.Connections are 2 data plus 1 clock, each sent as an LVDS 2-wire pair.Each LVDS wire-pair is run at 320 MHz. SoPEC is in a 100-pin QFP, with12 of those wires dedicated to the transmission of print data (6 wiresper printhead segment). Additional wires connect SoPEC to the printhead,but they are not considered for the purpose of this discussion.

The dot data is accepted by the printhead at 2-bits per cycle at 320MHz. 6 bits are available after 3 cycles at 320 MHz, and these 6-bitsare then clocked into the shift registers within the printhead at a rateof 106 MHz. Thus the data movement within the printhead shift registersis able to keep up with the rate at which data arrives in the printhead.

Issues introduced by printing at 60 ppm are now described, with thecases of 4, 5, and 6 colors in the printhead. The arrangement is shownin FIG. 39.

A 60 ppm printer is 1 page per second. i.e.,

-   -   A4=21,063 lines. This is a line rate of 21.06 KHz (a line time        of 47.4 us)    -   Letter=20,120 lines. This is a line rate of 20.12 KHz (a line        time of 49.7 us)        If each SoPEC is responsible for generating the data for its        specific printhead, then the worst case for dot generation is        the largest printhead. Since the preferred embodiment of SoPEC        is run at 160 MHz, it is only able to meet the dot requirement        rate for the 5:5 printhead, and not the 6:4 or 7:3 printheads.

Each SoPEC must transmit a printhead's worth of bits per color to theprinthead per line. The transmission time is further constrained by thefact that no data must be transmitted to the printhead segments during awindow around the linesync pulse. Assuming that the line sync overheadis constant regardless of print speed, then a 1% overhead at 30 ppmtranslates into a 2% overhead at 60 ppm. Since we have 2 lines to theprinthead operating at 320 MHz each, the total bandwidth available is640 Mb/sec. The existing connection to the printhead will only deliverdata to a 4-color 5:5 arrangement printhead fast enough for 60 ppm. Theconnection speed in the preferred embodiment is not fast enough tosupport any other printhead or color configuration.

The dot data is currently accepted by the printhead at 2-bits per cycleat 320 MHz. Although the connection rate is only fast enough for 4 color5:5 printing, the data must still be moved around in the shift registersonce received.

The 5:5 printer 4-color dot data is accepted by the printhead at 2-bitsper cycle at 320 MHz. 4 bits are available after 2 cycles at 320 MHz,and these 4-bits would then need to be clocked into the shift registerswithin the printhead at a rate of 160 MHz. Since the 6:4 and 7:3printhead configuration schemes require additional bandwidth etc., theprinthead needs some change to support these additional forms of 60 ppmprinting.

Given the problems described above, the following issues have beenaddressed for 60 ppm printing based on the earlier SoPEC architecture:

-   -   rate of data generation    -   transmission to the printhead    -   shift register setup within the printhead.        Assuming the current bi-lithic printhead, there are 3 basic        classes of solutions to allow 60 ppm:

-   a. Each SoPEC generates dot data and transmits that data to a single    printhead connection, as shown in FIG. 40.

-   b. One SoPEC generates data and transmits to the smaller printhead,    but both SoPECs generate and transmit directly to the larger    printhead, as shown in FIG. 41.

-   c. Same as (b) except that SoPEC A only transmits to printhead B via    SoPEC B (i.e. instead of directly), as shown in FIG. 42.

The Class A solution is where each SoPEC generates dot data andtransmits that data to a single printhead connection, as shown in FIG.40. The existing SoPEC architecture is targeted at this class ofsolution. Two methods of implementing a 60 ppm solution of this classare examined below.

To achieve 60 ppm using the same basic architecture as currentlyimplemented, the following needs to occur:

-   -   Increase effective dot generation rate to 206 MHz    -   Increase bandwidth to printhead to 1256 Mb/sec    -   Increase bandwidth of printhead shift registers to match        transmission bandwidth        It should be noted that even when all these speed improvements        are implemented, one SoPEC will still be producing 40% more dots        than it would be under a 5:5 scheme. i.e. this class of solution        is not load balanced.

Each SoPEC may generate data as if for a 5:5 printhead, and theprinthead, even though it is physically a 5:5, 6:4 or 7:3 printhead,maintains a logical appearance of a 5:5 printhead. There are a number ofmeans of accomplishing this logical appearance, but they all rely on thetwo printheads being connected in some way, as shown in FIG. 41. In thisembodiment, the dot generation rate no longer needs to be addressed asonly the 5:5 dot generation rate is required, and the current speed of160 MHz is sufficient.

The class B solution is where one SoPEC generates data and transmits tothe smaller printhead, but both SoPECs generate and transmit directly tothe larger printhead, as shown in FIG. 42. i.e. SoPEC A transmits toprintheads A and B, while SoPEC B transmits only to printhead B. Theintention is to allow each SoPEC to generate the dot data for a type 5printhead, and thereby to balance the dot generation load.

Since the connections between SoPEC and printhead are point-to-point, itrequires a doubling of printhead connections on the larger printhead(one connection set goes to SoPEC A and the other goes to SoPEC B). Thetwo methods of implementing a 60 ppm solution of this class depend onthe internals of the printhead, and are examined below.

The two connections on the printhead may be connected to the same shiftregister. Thus the shift register can be driven by either SoPEC, asshown in FIG. 43. The 2 SoPECs take turns (under synchronisation) intransmitting on their individual lines as follows:

-   -   SoPEC B transmits even (or odd) data for 5 segments    -   SoPEC A transmits data for 5-printhead A segments even and odd    -   SoPEC B transmits the odd (or even) data for 5 segments.        Meanwhile SoPEC A is transmitting the data for printhead A,        which will be length 3, 4, or 5.

Note that SoPEC A is transmitting as if to a printhead combination ofN:5−N, which means that the dot generation pathway (other thansynchronization) is already as defined. Although the dot generationproblem is resolved by this scenario (each SoPEC generates data for halfthe page width and therefore it is load balanced), the transmissionspeed for each connection must be sufficient to deliver to a type7printhead i.e. 1256 Mb/sec. In addition, the bandwidth of the printheadshift registers must be altered to match the transmission bandwidth.

The two connections on the printhead may be connected to different shiftregisters, as shown in FIG. 44. Thus the two SoPECs can write to theprinthead in parallel. Note that SoPEC A is transmitting as if to aprinthead combination of N:5−N, which means that the dot generationpathway is already as defined.

The dot generation problem is resolved by this scenario since each SoPECgenerates data for half the page width and therefore it is loadbalanced. Since the connections operate in parallel, the transmissionspeed required is that required to address 5:5 printing, i.e. 891Mb/sec. In addition, the bandwidth of the printhead shift registers mustbe altered to match the transmission bandwidth.

The class C solution is the same as that described for class B, exceptthat SoPEC A only transmits to printhead B via SoPEC B (i.e. instead ofdirectly), as shown in FIG. 45 i.e. SoPEC A transmits directly toprinthead A and indirectly to printhead B via SoPEC B, while SoPEC Btransmits only to printhead B.

This class of architecture has the attraction that a printhead is drivenby a single SoPEC, which minimizes the number of pins on a printhead.However it requires receiver connections on SoPEC B. It becomesparticularly practical (costwise) if those receivers are currentlyunused (i.e. they would have been used for transmitting to the secondprinthead in a single SoPEC system). Of course this assumes that thepins are not being used to achieve the higher bandwidth.

Since there is only a single connection on the printhead, the serialload scenario would be the mechanism for transfer of data, with the onlydifference that the connections to the printhead are via SoPEC B.Although the dot generation problem is resolved by this scenario (eachSoPEC generates data for half the page width and therefore it is loadbalanced), the transmission speed for each connection must be sufficientto deliver to a type7 printhead i.e. 1256 Mb/sec. In addition, thebandwidth of the printhead shift registers must be altered to match thetransmission bandwidth.

If SoPEC B provides at least a line buffer for the data received fromSoPEC A, then the transmission between SoPEC A and printhead A isdecoupled, and although the bandwidth from SoPEC B to printhead B mustbe 1256 Mb/sec, the bandwidth between the two SoPECs can be lower i.e.enough to transmit 2 segments worth of data (359 Mb/sec).

Architecture A has the problem that no matter what the increase inspeed, the solution is not load balanced, leaving architecture B or Cthe more preferred solution where load-balancing between SoPEC chips isdesirable or necessary. The main advantage of an architecture A stylesolution is that it reduces the number of connections on the printhead.All architectures require the increase in bandwidth to the printhead,and a change to the internal shift register structure of the printhead.

Other architectures can be used where different printhead modules areused. For example, in one embodiment, the dot data is provided from asingle printed controller (SoPEC) via multiple serial links to aprinthead. Preferably, the links in this embodiment each carry dot datafor more than one channel (color, etc) of the printhead. For example,one link can carry CMY dot data from the printer controller and theother channel can carry K, IR and fixative channels.

The basic idea of the linking printhead is that we create a printheadfrom tiles each of which can be fully formed within the reticle. Theprintheads are linked together as shown in FIG. 49 to form thepage-width printhead. For example, an A4/Letter page is assembled from11 tiles.

The printhead is assembled by linking or butting up tiles next to eachother. The physical process used for linking means that wide-formatprintheads are not readily fabricated (unlike the 21 mm tile). Howeverprinters up to around A3 portrait width (12 inches) are expected to bepossible.

The nozzles within a single segment are grouped physically to reduce inksupply complexity and wiring complexity. They are also grouped logicallyto minimize power consumption and to enable a variety of printingspeeds, thereby allowing speed/power consumption trade-offs to be madein different product configurations.

Each printhead segment contains a constant number of nozzles per color(currently 1280), divided into half (640) even dots and half (640) odddots. If all of the nozzles for a single color were fired atsimultaneously, the even and odd dots would be printed on differentdot-rows of the page such that the spatial difference between anyeven/odd dot-pair is an exact number of dot lines. In addition, thedistance between a dot from one color and the corresponding dot from thenext color is also an exact number of dot lines.

The exact distance between even and odd nozzle rows, and between colorswill vary between embodiments, so it is preferred that theserelationships be programmable with respect to SoPEC.

When 11 segments are joined together to create a 30 ppm printhead, asingle SoPEC will connect to them as shown in FIG. 50. Notice that eachphDataOutn lvds pair goes to two adjacent printhead segments, and thateach phClkn signal goes to 5 or 6 printhead segments. Each phRstn signalgoes to alternate printhead segments.

SoPEC drives phRst0 and phRst1 to put all the segments into reset. SoPECthen lets phRst1 come out of reset, which means that all the segment 1,3, 5, 7, and 9 are now alive and are capable of receiving commands.SoPEC can then communicate with segment 1 by sending commands downphDataOut0, and program the segment 1 to be id 1. It can communicatewith segment 3 by sending commands down phDataOut1, and program segment3 to be id 1. This process is repeated until all segments 1, 3, 5, 7,and 9 are assigned ids of 1. The id only needs to be unique per segmentaddressed by a given phDataOutn line.

SoPEC can then let phRst0 come out of reset, which means that segments0, 2, 4, 6, 8, and 10 are all alive and are capable of receivingcommands. The default id after reset is 0, so now each of the segmentsis capable of receiving commands along the same pDataOutn line.

SoPEC needs to be able to send commands to individual printheads, and itdoes so by writing to particular registers at particular addresses. Theexact relationship between id and register address etc. is yet to bedetermined, but at the very least it will involve the CPU being capableof telling the PHI to send a command byte sequence down a particularphDataOutn line.

One possibility is that one register contains the id (possibly 2 bits ofid). Further, a command may consist of:

-   -   register write    -   register address    -   data        A 10-bit wide fifo can be used for commands in the PHI.

When 11 segments are joined together to create a 60 ppm printhead, the 2SoPECs will connect to them as shown in FIG. 51. In the 60 ppm case onlyphClk0 and phRst0 are used (phClk1 and phRst1 are not required). Howevernote that lineSync is required instead. It is possible therefore toreuse phRst1 as a lineSync signal for multi-SoPEC synchronisation. It isnot possible to reuse the pins from phClk1 as they are lvds. It shouldbe possible to disable the lvds pads of phClk1 on both SoPECs andphDataOut5 on SoPEC B and therefore save a small amount of power.

The A-A chip printhead style consists of identical printhead tiles (typeA) assembled in such a way that rows of nozzles between 2 adjacent chipshave no vertical misalignment.

The most ideal format for this kind of printhead from a data deliverypoint of view is a rectangular join between two adjacent printheads, asshown in FIG. 52. However due to the requirement for dots to beoverlapping, a rectangular join results in a it results in a verticalstripe of white down the join section since no nozzle can be in thisjoin region. A white stripe is not acceptable, and therefore this jointype is not acceptable. FIG. 53 shows a sloping join similar to thatdescribed for the bi-lithic printhead chip, and FIG. 54 is a zoom in ofa single color component, illustrating the way in which there is novisible join from a printing point of view (i.e. the problem seen inFIG. 52 has been solved).

The A-chip/A-chip setup requires perfect vertical alignment. Due to avariety of factors (including ink sealing) it may not be possible tohave perfect vertical alignment. To create more space between thenozzles, A-chips can be joined with a growing vertical offset, as shownin FIG. 55. The growing offset comes from the vertical offset betweentwo adjacent tiles. This offset increases with each join. For example,if the offset were 7 lines per join, then an 11 segment printhead wouldhave a total of 10 joins, and 70 lines. To supply print data to theprinthead for a growing offset arrangement, the print data for therelevant lines must be present. A simplistic solution of simply holdingthe entire line of data for each additional line required leads toincreased line store requirements. For example, an 11 segment×1280-dotprinthead requires an additional 11×1280-dots×6-colors per line i.e.10.3125 Kbytes per line. 70 lines requires 722 Kbytes of additionalstorage. Considering SoPEC contains only 2.5 MB total storage, anadditional 722 Kbytes just for the offset component is not desirable.Smarter solutions require storage of smaller parts of the line, but thenet effect is the same: increased storage requirements to cope with thegrowing vertical offset.

The problem of a growing offset is that a number of additional lines ofstorage need to be kept, and this number increases proportional to thenumber of joins i.e. the longer the printhead the more lines of storageare required. However, we can place each chip on a mild slope to achievea constant number of printlines regardless of the number of joins. Thearrangement is similar to that used in PEC1, where the printheads aresloping. The difference here is that each printhead is only mildlysloping, for example so that the total number of lines gained over thelength of the printhead is 7. The next printhead can then be placedoffset from the first, but this offset would be from the same base. i.e.a printhead line of nozzles starts addressing line n, but moves todifferent lines such that by the end of the line of nozzles, the dotsare 7 dotlines distant from the startline. This means that the 7-lineoffset required by a growing-offset printhead can be accommodated. Thearrangement is shown in FIG. 56.

Note also, that in this example, the printhead segments are verticallyaligned (as in PEC1). It may be that the slope can only be a particularamount, and that growing offset compensates for additionaldifferences—i.e. the segments could in theory be misaligned vertically.In general SoPEC must be able to cope with vertically misalignedprinthead segments.

The question then arises as to how much slope must be compensated for at60 ppm speed. Basically—as much as can comfortably handled without toomuch logic. However, amounts like 1 in 256 (i.e. 1 in 128 with respectto a half color), or 1 in 128 (i.e. 1 in 64 with respect to a halfcolor) must be possible. Greater slopes and weirder slopes (e.g. 1 in129 with respect to a half color) must be possible, but with a sacrificeof speed i.e. SoPEC must be capable even if it is a slower print.

Note also that the nozzles are aligned, but the chip is placed sloped.This means that when horizontal lines are attempted to be printed and ifall nozzles were fired at once, the effect would be lots of slopedlines. However, if the nozzles are fired in the correct order relativeto the paper movement, the result is a straight line for n dots, thenanother straight line for n dots 1 line up.

The PEC1 style slope is the physical arrangement used by printheadsegments addressed by PEC1. Note that SoPEC is not expected to work at60 ppm speed with printheads connected in this way. However it isexpected to work and is shown here for completeness, and if tests shouldprove that there is no working alternative to the 21 mm tile, then SoPECwill require significant reworking to accommodate this arrangement at 60ppm.

In this scheme, the segments are joined together by being placed on anangle such that the segments fit under each other, as shown in FIG. 57.The exact angle will depend on the width of the Memjet segment and theamount of overlap desired, but the vertical height is expected to be inthe order of 1 mm, which equates to 64 dot lines at 1600 dpi. FIG. 58shows more detail of a single segment in a multi-segment configuration,considering only a single row of nozzles for a single color plane. Eachof the segments can be considered to produce dots for multiple sets oflines. The leftmost d nozzles (d depends on the angle that the segmentis placed at) produce dots for line n, the next d nozzles produce dotsfor line n−1, and so on.

In the A-chip/A-chip with inter-line slope compensation the nozzles arephysically arranged inside the printhead to compensate for the nozzlefiring order given the desire to spread the power across the printhead.This means that one nozzle and its neighbor can be vertically separatedon the printhead by 1 printline. i.e. the nozzles don't line up acrossthe printhead. This means a jagged effect on printed “horizontal lines”is avoided, while achieving the goal of averaging the power.

The arrangement of printheads is the same as that shown in FIG. 56.However the actual nozzles are slightly differently arranged, asillustrated via magnification in FIG. 59.

Another possibility is to have two kinds of printing chips: an A-typeand a B-type. The two types of chips have different shapes, but can bejoined together to form long printheads. A parallelogram is formed whenthe A-type and B-type are joined. The two types are joined together asshown in FIG. 60.

Note that this is not a growing offset. The segments of amultiple-segment printhead have alternating fixed vertical offset from acommon point, as shown in FIG. 61. If the vertical offset from a type-Ato a type-B printhead were n lines, the entire printhead regardless oflength would have a total of n lines additionally required in the linestore. This is certainly a better proposition than a growing offset).

However there are many issues associated with an A-chip/B-chipprinthead. Firstly, there are two different chips i.e. an A-chip, and aB-chip. This means 2 masks, 2 developments, verification, and differenthandling, sources etc. It also means that the shape of the joins aredifferent for each printhead segment, and this can also imply differentnumbers of nozzles in each printhead. Generally this is not a goodoption.

The general linking concept in the A-chip/B-chip above can beincorporated into a single printhead chip that contains the A-B joinwithin the single chip type. This kind of joining mechanism is referredto as the A-B chip since it is a single chip with A and Bcharacteristics. The two types are joined together as shown in FIG. 62.This has the advantage of the single chip for manipulation purposes.

A-B chip with printhead compensation is where we push the A-B chipdiscontinuity as far along the printhead segment as possible—right tothe edge. This maximises the A part of the chip, and minimizes the Bpart of the chip. If the B part is small enough, then the compensationfor vertical misalignment can be incorporated on the printhead, andtherefore the printhead appears to SoPEC as if it was a single typeAchip. This only makes sense if the B part is minimized since printheadreal-estate is more expensive at 0.35 microns rather than on SoPEC at0.18 microns. The arrangement is shown in FIG. 63.

Note that since the compensation is accomplished on the printhead, thedirection of paper movement is fixed with respect to the printhead. Thisis because the printhead is keeping a history of the data to apply at alater time and is only required to keep the small amount of data fromthe B part of the printhead rather than the A part.

Within reason, some of the various linking methods can be combined. Forexample, we may have a mild slope of 5 over the printhead, plus anon-chip compensation for a further 2 lines for a total of 7 linesbetween type A chips. The mild slope of 5 allows for a 1 in 128 per halfcolor (a reasonable bandwidth increase), and the remaining 2 lines arecompensated for in the printheads so do not impact bandwidth at all.

However we can assume that some combinations make less sense. Forexample, we do not expect to see an A-B chip with a mild slope.

SoPEC also caters for printheads and printhead modules that haveredundant nozzle rows. The idea is that for one print line, we fire fromnozzles in row x, in the next print line we fire from the nozzles in rowy, and the next print line we fire from row x again etc. Thus, if thereare any defective nozzles in a given row, the visual effect is halvedsince we only print every second line from that row of nozzles. Thiskind of redundancy requires SoPEC to generate data for differentphysical lines instead of consecutive lines, and also requiresadditional dot line storage to cater for the redundant rows of nozzles.

Redundancy can be present on a per-color basis. For example, K may haveredundant nozzles, but C, M, and Y have no redundancy. In the preferredform, we are concerned with redundant row pairs, i.e. rows 0+1 alwaysprint odd and even dots of the same colour, so redundancy would requiresay rows 0+1 to alternate with rows 2+3.

To enable alternating between two redundant rows (for example), twoadditional registers REDUNDANT_ROWS_0[7:0] and REDUNDANT_ROWS_1 [7:0]are provided at addresses 8 and 9. These are protected registers,defaulting to 0x00. Each register contains the following fields:

Bits [2:0]—RowPairA (000 means rows 0+1, 001 means rows 2+3 etc)

Bits [5:3]—RowPairB (000 means rows 0+1, 001 means rows 2+3 etc)

Bit [6]—toggleAB (0 means loadA/fireB, 1 means loadB/fireA)

Bit [7]—valid (0 means ignore the register).

The toggle bit changes state on every FIRE command; SoPEC needs to clearthis bit at the start of a page.

The operation for redundant row printing would use similar mechanism tothose used when printing less than 5 colours:

-   -   with toggleAB=0, the RowPairA rows would be loaded in the        DATA_NEXT sequence, but the RowPairB rows would be skipped. The        TDC FIFO would insert dummy data for the RowPairB rows. The        RowPairA rows would not be fired, while the RowPairB rows would        be fired.    -   with toggleAB=1, the RowPairB rows would be loaded in the        DATA_NEXT sequence, but the RowPairA rows would be skipped. The        TDC FIFO would insert dummy data for the RowPairA rows. The        RowPairB rows would not be fired, while the RowPairA rows would        be fired.

In other embodiments, one or more redundant rows can also be used toimplement per-nozzle replacement in the case of one or more deadnozzles. In this case, the nozzles in the redundant row only print dotsfor positions where a nozzle in the main row is defective. This may meanthat only a relatively small numbers of nozzles in the redundant rowever print, but this setup has the advantage that two failed printheadmodules (ie, printhead modules with one or more defective nozzles) canbe used, perhaps mounted alongside each other on the one printhead, toprovide gap-free printing. Of course, if this is to work correctly, itis important to select printhead modules that have different defectivenozzles, so that the operative nozzles in each printhead module cancompensate for the dead nozzle or nozzles in the other.

Whilst probably of questionable commercial usefulness, it is alsopossible to have more than one additional row for redundancy per color.It is also possible that only some rows have redundant equivalents. Forexample, black might have a redundant row due to its high visibility onwhite paper, whereas yellow might be a less likely candidate since adefective yellow nozzle is much less likely to produce a visuallyobjectionable result.

A dot generator will process zero or one or two segments, based on a twobit configuration. When processing a segment it will process the twelvehalf colors in order, color zero even first, then color zero odd, thencolor 1 even, etc. The LLU will know how long a segments is, and we willassume all segments are the same length.

To process a color of a segment the generator will need to load thecorrect word from dram. Each color will have a current base address,which is a pointer into the dot fifo for that color. Each segment has anaddress offset, which is added to the base address for the current colorto find the first word of that colour. For each generator we maintain acurrent address value, which is operated on to determine the locationfuture reads occur from for that segment. Each segment also has a startbit index associated with it that tells it where in the first word itshould start reading data from.

A dot generator will hold a current 256 bit word it is operating on. Itmaintains a current index into that word. This bit index is maintainedfor the duration of one color (for one segment), it is incrementedwhenever data is produced and reset to the segment specified value whena new color is started. 2 bits of data are produced for the PHI eachcycle (subject to being ready and handshaking with the PHI).

From the start of the segment each generator maintains a count, whichcounts the number of bits produced from the current line. The counter isloaded from a start-count value (from a table indexed by the half-colorbeing processed) that is usually set to 0, but in the case of the A-Bprinthead, may be set to some other non-zero value. The LLU has a slopespan value, which indicates how many dots may be produced before achange of line needs to occur. When this many dots have been produced bya dot generator, it will load a new data word and load 0 into the slopecounter. The new word may be found by adding a dram address offset valueheld by the LLU. This value indicates the relative location of the newword; the same value serves for all segment and all colours. When thenew word is loaded, the process continues from the current bit index, ifbits 62 and 63 had just been read from the old word (prior to slopeinduced change) then bits 64 and 65 would be used from the newly loadedword.

When the current index reaches the end of the 256 bits current dataword, a new word also needs to be loaded. The address for this value canbe found by adding one to the current address.

It is possible that the slope counter and the bit index counter willforce a read at the same time. In this case the address may be found byadding the slope read offset and one to the current address.

Observe that if a single handshaking is use between the dot generatorsand the PHI then the slope counter as used above is identical betweenall 6 generators, i.e. it will hold the same counts and indicate loadsat the same times. So a single slope counter can be used. However theread index differs for each generator (since there is a segmentconfigured start value. This means that when a generator encounters a256-bit boundary in the data will also vary from generator to generator.

The printhead will be designed for 5 colors. At present the intended useis:

-   -   cyan    -   magenta    -   yellow    -   black    -   infra-red

However the design methodology must be capable of targeting a numberother than 5 should the actual number of colors change. If it doeschange, it would be to 6 (with fixative being added) or to 4 (withinfra-red being dropped). The printhead chip does not assume anyparticular ordering of the 5 color channels.

The printhead will contain 1280 nozzles of each color—640 nozzles on onerow firing even dots, and 640 nozzles on another row firing odd dots.This means 11 linking printheads are required to assemble an A4/Letterprinthead. However the design methodology must be capable of targeting anumber other than 1280 should the actual number of nozzles per colorchange. Any different length may need to be a multiple of 32 or 64 toallow for ink channel routing.

The printhead will target true 1600 dpi printing. This means ink dropsmust land on the page separated by a distance of 15.875 microns. The15.875 micron inter-dot distance coupled with MEMs requirements meanthat the horizontal distance between two adjacent nozzles on a singlerow (e.g. firing even dots) will be 31.75 microns. All 640 dots in anodd or even color row are exactly aligned vertically. Rows are firedsequentially, so a complete row is fired in small fraction (nominallyone tenth) of a line time, with individual nozzle firing distributedwithin this row time. As a result dots can end up on the paper with avertical misplacement of up to one tenth of the dot pitch. This isconsidered acceptable.

The vertical distance between rows is adjusted based on the row firingorder. Firing can start with any row, and then follows a fixed rotation.FIG. 70 shows the default row firing order from 1 to 10, starting at thetop even row. Rows are separated by an exact number of dot lines, plus afraction of a dot line corresponding to the distance the paper will movebetween row firing times. This allows exact dot-on-dot printing for eachcolor. The starting row can be varied to correct for verticalmisalignment between chips, to the nearest 0.1 pixels. SoPEC appropriatedelays each row's data to allow for the spacing and firing order.

An additional constraint is that the odd and even rows for given colormust be placed close enough together to allow them to share an inkchannel. This results in the vertical spacing shown in FIG. 70, where Lrepresents one dot pitch.

Multiple identical printhead chips must be capable of being linkedtogether to form an effectively horizontal assembled printhead. Althoughthere are several possible internal arrangements, construction andassembly tolerance issues have made an internal arrangement of a droppedtriangle (ie a set of rows) of nozzles within a series of rows ofnozzles, as shown in FIG. 71. These printheads can be linked together asshown in FIG. 72.

Compensation for the triangle is preferably performed in the printhead,but if the storage requirements are too large, the triangle compensationcan occur in SoPEC. However, if the compensation is performed in SoPEC,it is required in the present embodiment that there be an even number ofnozzles on each side of the triangle.

It will be appreciated that the triangle disposed adjacent one end ofthe chip provides the minimum on-printhead storage requirements.However, where storage requirements are less critical, other shapes canbe used. For example, the dropped rows can take the form of a trapezoid.

The join between adjacent heads has a 45° angle to the upper and lowerchip edges. The joining edge will not be straight, but will have asawtooth or similar profile. The nominal spacing between tiles is 10microns (measured perpendicular to the edge). SoPEC can be used tocompensate for both horizontal and vertical misalignments of the printheads, at some cost to memory and/or print quality. Note also that papermovement is fixed for this particular design.

A print rate of 60 A4/Letter pages per minute is possible. The printheadwill assume the following:

-   -   page length=297 mm (A4 is longest page length)    -   an inter-page gap of 60 mm or less (current best estimate is        more like 15+/−5 mm        This implies a line rate of 22,500 lines per second. Note that        if the page gap is not to be considered in page rate        calculations, then a 20 KHz line rate is sufficient.

Assuming the page gap is required, the printhead must be capable ofreceiving the data for an entire line during the line time. i.e. 5colors 1280 dots 22,500 lines=144 MHz or better (173 MHz for 6 colors).

The printhead will most likely be inserted into a print cartridge foruser-insertion into the printer, similar to the way a laser-printertoner cartridge is inserted into a laser printer. In a home/officeenvironment, ESD discharges up to 15 kV may occur during handling. It isnot feasible to provide protection against such discharges as part ofthe chip, so some kind of shielding will be needed during handling. Theprinthead chip itself will target MIL-STD-883 class 1 (2 kV human bodymodel), which is appropriate for assembly and test in a anESD-controlled environment.

The SRM043 is a CMOS and MEMS integrated chip. The MEMSstructures/nozzles can eject ink which has passed through the substrateof the CMOS via small etched holes. The SRM043 has nozzles arranged tocreate a accurately placed 1600 dots per inch printout. The SRM043 has 5colors, 1280 nozzles per color. The SRM043 is designed to link to asimilar SRM043 with perfect alignment so the printed image has noartifacts across the join between the two chips.

SRM043 contains 10 rows of nozzles, arranged as upper and lower rowpairs of 5 different inks. The paired rows share a common ink channel atthe back of the die. The nozzles in one of the paired rows arehorizontally spaced 2 dot pitches apart, and are offset relative to eachother.

1600 dpi has a dot pitch of DP 15.875 m. The MEMS print nozzle unit cellis 2 DP wide by 5 DP high (31.75 m×79.375 m). To achieve 1600 dpi percolour, 2 horizontal rows of (1280/2) nozzles are placed with ahorizontal offset of 5 DP (2.5 cells). Vertical offset is 3.5 DP betweenthe two rows of the same colour and 10.1 DP between rows of differentcolour. This slope continues between colours and results in a print areawhich is a trapezoid as shown in FIG. 73. Within a row, the nozzles areperfectly aligned vertically.

For ink sealing reasons a large area of silicon beyond the end nozzlesin each row is required on the base of the die, near where the chiplinks to the next chip. To do this the first 4*Row#+4-2*(Row# mod 2)nozzles from each row are vertical shifted down DP. Data for the nozzlesin the triangle must be delayed by 10 line times to match the trianglevertical offset. The appropriate number of data bits at the start ofeach row are put into a FIFO. Data from the FIFO's output is usedinstead. The rest of the data for the row bypasses the FIFO.

SRM043 consists of a core of 10 rows of 640 MEMS constructed inkejection nozzles. Around each of these nozzles is a CMOS unit cell. Thebasic operation of the SRM043 is to

-   -   receive dot data for all colours for a single line    -   fire all nozzles according to that dot data

To minimise peak power, nozzles are not all fired simultaneously, butare spread as evenly as possible over a line time. The firing sequenceand nozzle placement are designed taking into account paper movementduring a line, so that dots can be optimally placed on the page.Registers allow optimal placement to be achieved for a range ofdifferent MEMs firing pulse widths, printing speeds and inter-chipplacement errors.

The MEMS device can be modeled as a resistor, that is heated by a pulseapplied to the gate of a large PMOS FET. The profile (firing) pulse hasa programmable width which is unique to each ink color. The magnitude ofthe pulse is fixed by the external Vpos supply less any voltage dropacross the driver FET.

The unit cell contains a flip-flop forming a single stage of a shiftregister extending the length of each row. These shift registers, oneper row, are filled using a register write command in the data stream.Each row may be individually addressed, or a row increment command canbe used to step through the rows.

When a FIRE command is received in the data stream, the data in all theshift register flip-flops is transferred to a dot-latch in each of theunit cells, and a fire cycle is started to eject ink from every nozzlethat has a 1 in its dot-latch.

The FIRE command will reset the row addressing to the last row. ADATA_NEXT command preceding the first row data will then fill the firstrow. While the firing/ejection is taking place, the data for the nextline may be loaded into the row shift registers. Due to the mechanismused to handle the falling triangle block of nozzles the followingrestrictions apply:

-   -   The rows must be loaded in the same order between FIRE commands.        Any order may be used, but it must be the same each time.    -   Data must be provided for each row, sufficient to fill the        triangle segment.

A fire cycle sequences through all of the nozzles on the chip, firingall of those with a 1 in their dot-latch. The sequence is one row at atime, each row taking 10% of the total fire cycle. Within a row, aprogrammable value called the column Span is used to control the firing.Each <span>'th nozzle in the row is fired simultaneously, then theirimmediate left neighbours, repeating <span>times until all nozzles inthat row have fired. This is then repeated for each subsequent row,according the row firing order described below. Hence the maximum numberof nozzles firing at any one time is 640 divided by <span>.

In the default case, row 0 of the chip is fired first, according to thespan pattern. These nozzles will all fired in the first 10% of the linetime. Next all nozzles in row 2 will fire in the same pattern, similarlythen rows 4, 6 then 8. Immediately following, half way through the linetime, row 1 will start firing, followed by rows 3,5,7 then 9. FIG. 78shows this for the case of Span=2.

The 1/10 line time together with the 10.1 DP vertical color pitch appearon paper as a 10 DP line separation. The odd and even same-color rowsphysically spaced 3.5 DP apart vertically fired half a line time apartresults on paper as a 3 DP separation.

A modification of the firing order shown in FIG. 78 can be used toassist in the event of vertical misalignment of the printhead whenphysically mounted into a cartridge. This is termed micro positioning.

FIG. 79 shows in general how the fire pattern is modified to compensatefor mounting misalignment of one printhead with respect to its linkingpartner. The base construction of the printhead separates the row pairsby slightly more than an integer times the dot Pitch to allow fordistributing the fire pattern over the line period. This architecturecan be exploited to allow micro positioning.

Consider for example the printhead on the right being placed 0.3 dotslower than the reference printhead to the left. The reference printheadif fired with the standard pattern.

TABLE 1 Worked microposition example, 0 vertical offset nozzle firingtime paper dot required nozzle order delay row position row data 0 0 0 00 0 2 1 0.1 10.1 10.1 −10 4 2 0.2 20.2 20.2 −20 6 3 0.3 30.3 30.3 −30 84 0.4 40.4 40.4 −40 1 5 0.5 3.5 3.5 −3 3 6 0.6 13.6 13.6 −13 5 7 0.723.7 23.7 −23 7 8 0.8 33.8 33.8 −33 9 9 0.9 43.9 43.9 −43

TABLE 2 Worked microposition example, offset 0.3 down nozzle requiredFiring time paper dot row nozzle order delay row position data 0 7 0.7 0−0.3 1 2 8 .8 10.1 9.8 −9 4 9 0.9 20.2 19.9 −19 6 0 0 30.3 30 −30 8 10.1. 40.4 40.1 −40 1 2 0.2 3.5 3.2 −3 3 3 0.3 13.6 13.3 −13 5 4 0.4 23.723.4 −23 7 5 0.5 33.8 33.5 −33 9 6 0.6 43.9 43.6 −43In Tables 1 and 2:

-   -   the nozzle column shows the name of the nozzle    -   the firing order column shows the order the nozzles should fire        in    -   the time delay shows the fraction of a dot pitch the paper has        moved since the start of the fire cycle. It is the firing order        divided by the number of rows.    -   the nozzle paper row is the vertical offset to the nozzle, from        the printhead geometry    -   the dot position shows where the nozzle lines up on the page, it        is the nozzle paper row-printhead vertical offset.    -   the required row data column indicates what row data set should        be loaded in the row shift register. It is the time delay-dot        position, and should always be an integer.

This scheme can compensate for printhead placement errors to 1/10 dotpitch accuracy, for arbitrary printhead vertical misalignment. TheVPOSITION register holds the row number to fire first. The printheadperforms sub-line placement, the correct line must be loaded by SoPEC.

The width of the pulse that turns a heater on to eject an ink drop iscalled the profile.

The profile is a function of the MEMs characteristics and the inkcharacteristics. Different profiles might be used for different colors.Optimal dot placement requires each line to take 10% of the line time.to fire. So, while a row for a color with a shorter profile could intheory be fired faster than a color with a longer profile, this is notdesirable for dot placement.

To address this, the fire command includes a parameter called thefireperiod. This is the time allocated to fire a single nozzle,irrespective of its profile. For best dot placement, the fireperiodshould be chosen to be greater than the longest profile. If a profile isprogrammed to be longer than a fireperiod, then that nozzle pulse willbe extended to match the profile. This extends the line time, it doesnot affect subsequent profiles. This will degrade dot placement accuracyon paper.

The fireperiod and profiles are measured in wclks. A wclk is aprogrammable number of 288 Mhz clock periods. The value written tofireperiod and profile registers should be one less than the desireddelay in wclks. These registers are all 8 bits wide, so periods from 1to 256 wclks can be achieved. The Wclk prescaler should be programmedsuch that the longest profile is between 128 and 255 wclks long. Thisgives best line time resolution.

The ideal value for column span and fireperiod can be chosen based onthe maximum profile and the linetime. The linetime is fixed by thedesired printing speed, while the maximum profile depends on ink andMEMs characteristics as described previously. To ensure that all nozzlesare fired within a line time, the following relationship must be obeyed:# rows*columnspan*fireperiod<linetimeTo reduce the peak Vpos current, the column span should be programmed tobe the largest value that obeys the above relationship. This meansmaking fireperiod as small as possible, consistent with the requirementthat fireperiod be longer than the maximum profile, for optimal dotplacement.

As an example, with a 1 uS maximum profile width, 10 rows, and 44 usdesired row time a span of 4 yields 4*10*1=40 uS minimum time. A span of5 would require 50 uS which is too long.

Having chosen the column span, the fireperiod should be adjusted upwardfrom its minimum so that nozzle firing occupies all of the availablelinetime. In the above example, fireperiod would be set to 44us/(4*10)=1.1 uS. This will produce a 10% gap between individualprofiles, but ensures that dots are accurately placed on the page. Usinga fireperiod longer or shorter than the scaled line time will result ininaccurately placed ink dots.

The fireperiod to be used is updated as a parameter to every FIREcommand. This is to allow for variation in the linetime, due to changesin paper speed. This is important because a correctly calculatedfireperiod is essential for optimal dot placement.

If a FIRE command is received before a fire cycle is complete, the errorbit NO_EARLY_ERR is set and the next fire cycle is started immediately.The final column(s) of the previous cycle will not have been fullyfired. This can only occur if the new FIRE command is given early thanexpected, based on the previous fireperiod.

The profile pulse can only be a rectangular pulse. The only controlsavailable are pulse width and how often the nozzle is fired.

A nozzle can be fired rapidly if required by making the column span 1.Control of the data in the whole array is essential to select whichnozzle[s] are fired. Using this technique, a nozzle can be fired for1/10 of the line period. Data in the row shift registers must be used tocontrol which nozzles are unclogged, and to manage chip peak currents.It is possible to fire individual nozzles even more rapidly by reducingthe profile periods on colors not being cleared, and using a shortfireperiod.

The program registers generally require multiple bytes of data. and willnot be stable until the write operation is complete. An incomplete writeoperation (not enough data) will leave the register with an unknownvalue.

Sensitive registers are write protected to make it more difficult fornoise or transmission errors to affect them unintentionally. Writes toprotected registers must be immediately preceded with a UNPROTECTcommand. Unprotected registers can be written at any time. Reads are notprotected.

A fire cycle will be terminated early when registers controlling fireparameters are written. Hence these registers should preferably not bewritten while printing a page. Readback of the core requires the user tosuspend core write operations to the target row for the duration of therow read. There is no ability to directly read the TDC fifo. It may beindirectly read by writing data to the core with the TDC fifo enabled,then reading back the core row. The triangle sized segment at the startof the core row will contain TDC fifo data.

Reads are performed bit serially, using the read address command toselect a register, and the read_next command repeatedly to step throughthe register bits sequentially from bit 0. While reading, part or all ofa register may be read prior to issuing the read done command. Registerbits which are currently undefined will read X.

The printhead is little-endian. Bit order is controlled by the 8B/10Bencode on write, and is LSB first on read. Byte 0 is the leastsignificant byte and is sent first. Registers are a varying number ofbytes deep, ranging from 0 (unprotect) to 80 (any core row).

The printhead should be powered up with RstL low. This ensures that theprinthead will not attempt to fire any nozzle due to the unknown stateof power up. This will put registers into their default state (usuallyzero). RstL may be released after 3 Clk cycles, and IDLE symbols shouldbe send to the printhead.

During these IDLE symbols, the printhead will find the correct delay tocorrectly sample the Data. Once communication is established, functionalregisters can be programmed and status flags initialized. For amulti-drop Data, RstL should be deasserted for one chip at a time, andthat chip given a unique DEVICE ID with a write to that register. Thelast chip may keep the default DEVICE ID. After this step all chips canbe addressed, either separately or by broadcast as desired. A broadcastwrite may be used to set system parameters such as FIRE, PULSE PROFILE,MAIN and ENABLE.

Data is written to the core one row at a time. Data is written to therow indexed by ROW ADDRESS, using the data symbols following a write tothe DATA_RESUME or DATA_NEXT register. It is also possible to interruptthis data transfer phase with another (not row data) register write. UseDATA_RESUME to continue the data transfer after the interruption iscompleted. Only the first 640 bits of data sent to the current row areused, further data is ignored.

In this mode data to the core should be written with the DATA_NEXTcommand. DATA_RESUME is used if a complete transfer is interrupted. AFIRE command or RstL leaves the ROW ADDRESS in the correct state forthis method to work correctly.

FIG. 82 shows the top levels of the block diagram and by extension thetop wrapper netlist for the printhead. The modules comprising thelinking printhead CMOS are:

The core contains an array of unit cells and the column shift register(columnSR). The Unit Cell is the base structure of the printhead,consisting of one bit of the row data shift register, a latch to doublebuffer the data, the MEMS ink firing mechanism, a large transistor todrive the MEMS and some gates to enable that transistor at the correcttime. The column shift register is at the bottom of the core unit cellarray. It is used to generate timing for unit cell firing, inconjunction with the Fire and Profile Generator (FPG);

The Triangle Delay Compensation (TDC) module handles the loading of datainto row shift registers of the core. The dropped triangle at the lefthand end of the core prints 10 lines lower on the page than the bulk ofeach row. This implies data has to be delayed by 10 line times beforeink ejection. To minimize overhead on the print controller, and to makethe interface cleaner, that delay is provided on chip. The TDC blockconnects to a fifo used to store the data to be delayed, and routes thefirst few nozzle data samples in a particular row with data through thefifo. All subsequent data is passed straight through to the row shiftregisters. The TDC also serializes 8 bit wide data at the symbol rate of28.8 MHz to 2 bit nibbles at a 144 MHz rate, routes that data to all rowshift registers, and synchronously generates gated clocks for theaddressed row shift register;

The FPG controls the firing sequence of the nozzles on a row and columnbasis, and the width of the firing pulses applied to each actuator. Itproduces timed profile pulses for each row of the core. It alsogenerates clock and data to drive the ColumnSR The column enables fromthe ColumnSR, the row profile, and the data within the core are alland'ed together to fire the unit cell actuators and hence eject ink. TheFPG sequences the firing to produce accurate dot placement, compensatingfor printhead position and generates correct width profiles;

The Data EXtractor converts the input data stream into byte-wide commandand data symbols to the Command Unit (CU). It interfaces with afull-custom Datamux to sample data presented to the chip at the optimumeye. This data is then descrambled, symbols are aligned anddeserialized, and then decoded. Data and symbol type is passed to theCU;

The CU contains most of the control registers. It is responsible forimplementing the command protocol, and routes control and data andclocks to the rest of the chip as appropriate. The CU also contains allBIST functionality. The CU synchronizes reset_n for the rest of thechip. Reset is removed synchronously, but is applied to flip flops onthe async clear pin. Fire enable is overridden with an asynchronousreset signal; and

The chip has high speed clock and data LVDS pads connected to the DEXmodule. There is a Reset_n input and a modal tristate/open drain outputmanaged by the CU. There are also a number of ground pads, VDD pads andalso VPOS pads for the unit cell. The design should have no powersequencing requirements, but does require reset_n to be asserted atpower on. Lack of power sequencing requires that the ESD protection inthe pads be to ground, there cannot be diodes between the VPOS and VDDrails. Similarly the level translator in the unit cell must ensure thatthe PMOS switching transistor is off in the event VPOS is up before VDD.

The normal operation of the linking printhead is:

reset the head

program registers to control the firing sequence and parameters

load data for a single print line into (up to) 10 rows of the printhead

send a FIRE command, which latches the loaded data, and begins a firecycle

while the fire cycle is in progress, load data for the next print line

if the page is not finished, goto 4.

Note the spacing of FIRE commands determines the printing speed (inlines/second). The printhead would normally be set up so that a firecycle takes all of the time available between FIRE commands.

A Memjet printhead chip consists of an array of MEMs ejection devices(typically heaters), each with associated drive logic implemented inCMOS. Together the ejection device and the drive logic comprise a “unitcell”. Global control logic accepts data for a line to be printed in theform of a stream of fire bits, one bit per device. The fire bits areshifted into the array via a shift register. When each unit cell has thecorrect fire data bit, the control logic initiates a firing sequence, inwhich each ejection device is fired if its corresponding fire bit is a1, and not fired if its corresponding fire bit is a 0.

Ejection devices can suffer damage over time, due to

-   -   latent manufacturing defects    -   temporary environment conditions (such as depriming or temporary        blockage)    -   permanent environment conditions (permanent blockage)        Generally the damage is associated with the device getting        excessively hot.

As the devices rely on self-cooling to operate correctly, there is avicious cycle: a hot device is likely to malfunction (e.g. to deprime,or fail to eject a drop when fired), and a malfunctioning device islikely to become hot. Also, a malfunctioning device can generate heatthat flows to adjacent (good) devices, causing them to overheat andmalfunction. Damaged or malfunctioning ejection devices (heaters)generally also exhibit a variation in the resistivity of the heatermaterial.

Continued operation of a device at excess temperature can causepermanent damage, including permanent total failure. Therefore it isuseful to detect temperature, and/or conditions that may lead to excesstemperature, and use this information to temporarily or permanentlysuppress the firing operation of a device or devices. Temporarilysuppressing firing is intended to allow a device to cool, and/or anotheradverse condition such as depriming to clear, so that the device cansubsequently resume correct firing. Permanently suppressing firing stopsa damaged device from generating heat that affects adjacent devices.

The basis of the temperature (or other) detection is the variation of ameasurable parameter with respect to a threshold. This provides a binarymeasurement result per sensor—a negative result indicates a safecondition for firing, a positive result indicates that the temperaturehas exceeded a first threshold which is a potentially dangerouscondition for firing. The threshold can be made variable via the controllogic, to allow calibration.

A direct thermal sensor would include a sensing device with a knowntemperature variation co-efficient; there are many well-known techniquesin this area. Alternatively we can detect a change in the ejectiondevice parameters (e.g. resistivity) directly, without it necessarilybeing attributable to temperature.

Temperature sensing is possible using either a MEMs sensing device aspart of the MEMs heater structure, or a CMOS sensing device included inthe drive logic adjacent to the MEMs heater. Depending on requirements,a sensing device can be provided for every unit cell, or a sensingdevice per group (2, 4, 8 etc.) of cells. This depends on the size andcomplexity of the sensing device, the accuracy of the sensing device,and on the thermal characteristics of the printhead structure.

As mentioned, the sensing devices give a positive or negative result percell or group of cells. There are a number of ways to use this data tosuppress firing. In the simplest case, firing is suppressed directly inthe unit cell driving logic, based on the most recent sensing result forthat cell, by overriding the firing data provided by externalcontroller.

Alternatively, the sensing result can be passed out of the unit cellarray to the control logic on the printhead chip, which can thensuppress firing by modifying the firing data shifted into the cell forsubsequent lines. One method of passing the results out of the arraywould be to load it each cell's sensing result into the existing shiftregister, and shift the sensor results out as new firing data is beingshifted in. Alternatively a dedicated circuit can be used to pass theresults out.

The control logic could use the raw sensing results alone to make thedecision to suppress firing. Alternatively, it could combine theseresults with other data, for example:

-   -   allow a programmable override, i.e. ignore the sensor results,        either for a region or the whole chip    -   process groups of sensing results to make decisions on which        cells should not be fired    -   use and algorithm based on cumulative sensor results over time.        In addition to operations on the printhead, sensing results (raw        or processed/summarised) can be fed back to SoPEC (or other high        level device controlling the printhead), for example to update        the dead nozzle map, or change printhead parameters.

One way of doing this is to use the shift register used to shift in thedot data. For example, the clock signal that causes the values in theshift register to be output to the buffer can also trigger the shiftregisters to load the thermal values relating to the various nozzles.These thermal values are shifter out of the shift register as new dotdata is shifted in.

The thermal signals can be stored in memory and use to effectmodifications to operation of one or more nozzles where thermal problemsare identified. However, it is also possible to provide the output ofthe shift register to the input of an AND gate. The other input to theAND gate is the dot data to be clocked in. At any particular time, thedot data at the input to the AND gate corresponds with the thermal datafor the nozzle for which the dot data is destined. In this way, the dotdata is only loaded, and the nozzle enabled, if the thermal dataindicates that there is no thermal problem with the nozzle. A second ANDgate can be provided as a global enable/disable mechanism. The secondAND gate accepts an enable signal and the output of the shift registeras inputs, and outputs its result to the input of the first AND gate. Inthis embodiment, the other input to the AND gate is the current dotdata.

Depending upon the implementation, the nozzle or nozzles can bereactivated once the temperature falls to or below the first threshold.However, it may also be desirable to allow some hysteresis by setting asecond threshold lower than first and only enabling the nozzle ornozzles once the second threshold is reached.

It is possible to use SoPEC to send dot data to a printhead that isusing less than its full complement of rows. For example, it is possiblethat the fixative, IR and black channels will be omitted in a low end,low cost printer. Rather than design a new printhead having only threechannels, it is possible to select which channels are active in aprinthead with a larger number of channels (such as the presentlypreferred channel version). It may be desirable to use a printhead whichhas one or more defective nozzles in up to three rows as a printhead (orprinthead module) in a three color printer. It would be disadvantageousto have to load empty data into each empty channel, so it is preferableto allow one or more rows to be disabled in the printhead.

The printhead already has a register that allows each row to beindividually enabled or disabled (register ENABLE at address 0).Currently all this does is suppress firing for a non-enabled row.

To avoid SoPEC needing to send blank data for the unused rows, thefunctionality of these bits is extended to:

-   1. skip over disabled rows when DATA_NEXT register is written;-   2. force dummy bits into the TDC FIFO for a disabled rows,    corresponding to the number of nozzles in the dropped triangle    section for that row. These dummy bits are written immediately    following the first row write to the fifo following a fire command.

Using this arrangement, it is possible to operate a 6 color printhead asa 1 to 6 color printhead, depending upon which mode is set. The mode canbe set by the printer controller (SoPEC); once set, SoPEC need only senddot data for the active channels of the printhead.

It will be appreciated by those skilled in the art that the foregoingrepresents only a preferred embodiment of the present invention. Thoseskilled in the relevant field will immediately appreciate that theinvention can be embodied in many other forms.

1. A printer comprising: a printhead having ejection nozzles; and aplurality of controllers configured to process print data for printingand to output the processed data to the printhead, the plurality ofcontrollers being connected to a common input of the printhead.
 2. Aprinter according to claim 1, further comprising at least onesynchronization means between the plurality of controllers forsynchronizing the output of processed data thereby.
 3. A printeraccording to claim 1, configured such that the plurality of controllerssequentially output processed data to the common input.
 4. A printeraccording to claim 1, comprising another printhead having ejectionnozzles, wherein one of the plurality of controllers outputs processeddata to both printheads and another of the plurality of controllersoutputs processed data to one of the printheads.
 5. A printer accordingto claim 4, wherein the printheads are configured such that no datapasses between them.
 6. A printer according to claim 1, wherein theprinthead is a pagewidth printhead.
 7. A printer according to claim 1,wherein the controllers are configured to receive print data to beprinted using at least two different inks and control data forcontrolling printing of the print data.